Posted Nov 20, 2008 13:46 UTC (Thu) by rwmj (subscriber, #5474)
[Link]
I packaged boost. Boost is a classic example of an upstream package where they've gone off and written their own build system, so they have to maintain all the complexity of building on every system out there, and I had to add to that complexity for cross-compiling. I also did another C++ network environment called POCO, and they also wrote their own build system, completely different from the boost one obviously.
C++ programmers, eh - haven't they suffered enough already?
Posted Nov 20, 2008 22:50 UTC (Thu) by nix (subscriber, #2304)
[Link]
Cross-compiling and Boost.Jam? You have a stronger soul than I. Just
changing CFLAGS and the preferred installation prefix was hell, and then I
had to figure out why jam coredumped as soon as it started... Autoconf
may be nasty but it's a lot kinder to packagers/builders than bloody jam.
While KDE was searching for a new build system for KDE4 I was in terror
that they'd choose Boost.Jam because it was used for a successful C++
project. Thankfully they are not utterly insane and chose something nicer
(now with added lowercase! ;)))) )
select
Posted Nov 21, 2008 8:50 UTC (Fri) by aleXXX (subscriber, #2742)
[Link]
Initial support for building Boost using CMake has been committed to the
Boost repository a few weeks ago.
Alex
select
Posted Nov 22, 2008 12:34 UTC (Sat) by nix (subscriber, #2304)
[Link]