Quote:
Originally Posted by AustinSchuh
I already got GCC 4.5.3 compiling on Linux and targeting the cRIO. My patches and build script are here. Thanks to Ross Light for cleaning it up and getting it to run on OSX. It is unsupported, but seems to work well. This also builds my own version of libstdc++v3 that seems to work on the cRIO. It would be nice to integrate this into ucpp at some point.
http://hg.zombiezen.com/vxworks-gcc-patches/overview |
That's awesome that you have a newer version of GCC. I personally would *love* to be able to use some of the new features of C++11 (I've already gotten used to using them in my personal code, and it's kind of sad that I can't use them on FRC code), but I have reservations.
Primarily, I know that in order to pass inspection your robot must be running a certain version of the firmware. Now, I know that you could image the cRIO and then overwrite all of the libraries, but could you be disqualified for doing this? Anyone happen to know what the rules say on this? GCC 3 is so old... it seems like FIRST *should* encourage teams to innovate.
Also, at some point maybe I could modify ucpp to allow users to optionally install ucpp for their whole system. We could also look at integrating build scripts - if nothing else we could find the source for the same version of GCC that gccdist uses - this _in_theory_ should not have any issues and be fully compatible with the stock image.