Quote:
Originally Posted by Spectare
I don't really have any experience with CMake, that's why I wrote a makefile. If I have time I'll learn and submit a pull request with deploy capabilities.
|
You should, CMake is awesome. WPILib is compiled with it as it is actually a build system generator. Tell it your sources and what you want to happen, and then anyone can compile it using standard makefiles, mingw/msys makefiles, nmake, eclipse, netbeans, qt creator, or another build system.
Quote:
Originally Posted by Spectare
So does the FRC toolchain just use the armel gcc with links to NI libraries? I haven't delved deep into gcc before but that's what it looked like when I was browsing your repository.
|
Its a near-stock GCC build for the armel target on linux. The only thing NI-specific is the build of the linux-headers and eglibc library, but are otherwise mostly stock. Before I got everything worked out, I was able to successfully run with pure stock linux-headers and eglibc sources, but that caused some warnings when debugging. GDB and binutils are pure stock, no patches applied. The only patch on GCC is to change the output name of libstdc++ so we can use the latest C++14 features while the system still uses the old version it was tested against:
https://bitbucket.org/byteit101/tool...ame?at=default This makes upgrades very easy so we won't be stuck with ancient versions of GCC like Windriver with GCC 3.4.