Quote:
Originally Posted by rbmj
I'll upload the other files, which should help with building everything. These include .orig.tar.gz and .debian.tar.gz files IIRC.
The .orig files can be made with the following process with a git archive:
Code:
# in git archive for package $PKG
mkdir ../$PKG-$VERSION
git archive master | tar -x -C ../$PKG-$VERSION
cd ..
tar -cf $PKG_$VERSION.orig.tar $PKG-$VERSION
gzip $PKG_$VERSION.orig.tar
cd $PKG-$VERSION
debuild
Making these packages can be a pain in the rear. The debian/rules makefiles for gcc and wpilib are not code snippets I'm particularly proud of... but they work.
Also, if you make a mistake and the build dies, debian wants to completely rebuild the whole package from a distclean. So don't mess up when you're compiling GCC... you wouldn't believe how much time I wasted only to learn that I forgot to pass -e WIND_BASE to debuild...
|
I did the same thing, luckily, the first thing I did was check the config.log!
Regardless, ironically, I've got this stuff running on my mac via a manual install much better than I do on debian with the packages, but I'd love to help with development, and I want to stay current so I'm trying to switch over. Right now, theres something broken where its not finding the C++ includes (i.e. #include <string> won't work, etc) and I have no idea why. If anybody has run in to this, I'd appreciate a tip. Debugging as you're reading.
Also, just as a thought, since your debian package for wpilib has a builddep for cmake, and AFAIK, just invokes it, why don't you just use CPack? Seems like that would be a little bit cleaner solution, but that's just me.
EDIT: Still having that issue with the packages. I'm going to try the packages you built and see if that makes a difference. Just to make sure, I've been installing them in this order:
Code:
binutils
wrs-headers
gcc
buildscripts
Any help is appreciated.