View Single Post
  #10   Spotlight this post!  
Unread 27-01-2010, 16:59
jhersh jhersh is offline
National Instruments
AKA: Joe Hershberger
FRC #2468 (Appreciate)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 1997
Location: Austin, TX
Posts: 1,006
jhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond repute
Re: Compressor Code causes No Robot Code Error

Quote:
Originally Posted by sircedric4 View Post
We built it off the IterativeRobot example.
Just to be clear, you are referring to the "FRC Default Program" (as listed in the examples) aka "BuiltinDefaultCode" (as listed in the Project Explorer)? I double checked this project and it definitely includes the -mlongcall option.

Quote:
Originally Posted by sircedric4 View Post
But when I was copying that and pasting it and changing the name to our version control it wasn't taking information from the new directory so I was deleting the old build targets and creating new build targets. Could that have removed the magic "mlongcall" thing?
I tried removing the build targets and creating a new one and it still had the -mlongcall setting there.

Quote:
Originally Posted by sircedric4 View Post
I swear I am starting to feel like a caveman looking at magic. Any sufficiently advance technology being indistinguishable from magic. I feel like I am learning a specific chant to get specific outcomes. I'm glad we got wizards here that I can at least get answers on which magic chant to do for any given outcome. Thanks guys. I'll setup the project like outlined above and let you know if that solves our problems.
I know it seems like witchcraft, but it really is just an option for the PowerPC platform that can save space if your code is not huge. WPILib is huge... well... huge enough to need longcalls. We anticipated this issue and made it use the whole memory space by default. Really what we need to track down is how you lost that option in your project.

-Joe
Reply With Quote