No Robot Code may be caused by link error

[bob.wolff68]

Wow - it was obvious from the messages in the console that it was doing dynamic loading - otherwise I can't imagine it running at all. But I gotta say firstly I'm shocked we haven't run headlong into such issues in the past - lucky us. And secondly I gotta think that there are some good number of teams out there who have no idea what went wrong one day with their code and it no longer works...that's gotta be very frustrating. Seems to be very counterproductive for the goals of FIRST to me. It wouldn't be very hard to hard a 'whitelist' of expected runtime-load-symbols and have the compiler/linker at least WARN users if they have any unresolved symbols which are NOT part of the whitelist. This would provide sophisticated teams the ability to utilize runtime binding and keep junior teams from hurting themselves badly with what is nothing but a 'bug' to those teams.

Who maintains a FAQ or the Sticky threads here? This topic could be a notable for that -- "No Robot Code after deploy and reboot" ...

bob