View Single Post
  #6   Spotlight this post!  
Unread 01-05-2012, 19:44
rbmj rbmj is offline
Registered User
FRC #0612 (Chantilly Robotics)
Team Role: Alumni
 
Join Date: Apr 2011
Rookie Year: 2011
Location: DC Area/Fairfax County
Posts: 192
rbmj is a jewel in the roughrbmj is a jewel in the roughrbmj is a jewel in the rough
Re: Custom C++ Toolchain

OK. I'm looking for some advice:

Currently I have some statically linked binaries up. I'm worried, though, because those also include the system headers, which I don't have the right to redistribute. Should I take those binaries down and require everyone to use the build script?

I couldn't find a contact at WindRiver for FRC, so I guess I'll have to email their generic inquiry account. Maybe this can be easily resolved.

They also do some weird stuff with their include directories, that I'd ideally like to move around to simplify installation of GCC, as right now there's some hackish stuff I have to do to get GCC to build right :-(



--------



Also, I forgot to post instructions for the build script.

You need to call it like this:

/path/to/build/script/build.bash PREFIX DLDIR SRCDIR BUILDDIR

Where:
PREFIX is where to install everything to (e.g. /usr/local)
DLDIR is where to put the downloaded tarballs
SRCDIR is where to extract the sources
BUILDDIR is where to put the build trees.

Note that these should be absolute paths. If you're in a clean directory, this should be sufficient:

# ../build.bash /usr/local `pwd`/download `pwd`/src `pwd`/build

It also needs to be run as root. If you have build problems let me know.