[bob.wolff68]

Ken,

Our robot experienced a similar and even more dramatic version of this yesterday. Somehow (unrelated), our project file from last year no longer had two <class>.cpp files in the left hand project area. Therefore, those cpp files were not being compiled...no problem yet... and the main robot did instantiate both of these classes. Compile time won't notice a problem here, but linking *SHOULD*. It didn't. It compiles and links without issue. It gives a .out file. The .out file is happy to deploy. No robot code...

After a bit of investigating, we brought up NetConsole client - thanks for this tool - very helpful. At run-time, the .out file is ran, and it actually spits out errors about unresolved symbols which are all related to the non-compiled classes. *SIGH* - including the files in the project now yields a .out file that runs. It's not happy for other reasons which we'll explore today, but there's robot code.

What happened here folks? WindRiver want to comment? And I'd love to hear from FIRST as to why the toolchain hasn't changed since 2012. Is this a hint of big changes to come in platform, tools, etc? Rather surprised that we're using the same tools after a year ... and that the linker doesn't catch these issues more importantly.

Thanks,
bob