|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#3
|
|||
|
|||
|
Re: Custom C++ Toolchain
The CMake Toolchain file should work with the standard "gccdist" toolchain. If you download this toolchain <1> then the cmake file should work fine (NOTE: It requires munch.sh and strip_syms.sh from the vxworks-gcc-patches repo to be installed in WIND_BASE - maybe should make these a separate package), just set TOOLCHAIN_IS_GCCDIST to true.
The cmake toolchain file would work on windows if it weren't for the fact that I haven't bothered to create windows equivalents of munch.sh and strip_syms.sh. I don't know batch (or maybe it would have to be vbscript...) very well, so I wouldn't know how to substitute the cut and sed commands. If I can get the cmake scripts working on windows that opens up the possibility of teams using those dreamspark cards and developing the robot in visual studio, or codeblocks for FOSS purists like myself ![]() I don't know if the generators for VS or C::B support manual target rules though (CMAKE_C_COMPILE_OBJECT et al). Side note: I'm thinking in the future this can be four packages: vxworks-binutils vxworks-gcc (depends vxworks-binutils) vxworks-scripts (depends vxworks-binutils) vxworks-cmake-toolchain (depends vxworks-scripts, vxworks-gcc, vxworks-binutils) Maybe have a PPA... So question: Should I keep statically linking the binaries so they work on most linuxes, or should I use "proper" packaging? Also, if anyone gets a chance to test this with a machine other than my own, that would be cool maybe get it to work on win32? MSYS seems like the best option...1. ftp://ftp.ni.com/pub/devzone/tut/updated_vxworks63gccdist.zip" |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|