CMake has a great book published that tells a lot of stuff. CMake has
a great Mailing list were users exchange information constantly, and
As an update, the third edition of the book was sent to the printers a few
weeks ago and should be in stock either Friday this week or early next week.
It
John Biddiscombe wrote:
I know the subject has come up a couple of times... I'm fed up with
having to install boost on every system I have to compiled something on.
I'd like to have a Boost utility dir in my source which will build
itself along with all the other cmake controlled projects.
And I'll chime in that I've CMakeified the boost threading library,
and it was pretty trivial. I put the header files in one place, and
listed all the .cpp files in libs/thread/src into a library target. I
changed config/user.hpp to define BOOST_ALL_NO_LIB to supress their
library version
And I'll chime in that I've CMakeified the boost threading library,
and it was pretty trivial. I put the header files in one place, and
listed all the .cpp files in libs/thread/src into a library target. I
changed config/user.hpp to define BOOST_ALL_NO_LIB to supress their
library version
I know the subject has come up a couple of times... I'm fed up with
having to install boost on every system I have to compiled something on.
I'd like to have a Boost utility dir in my source which will build
itself along with all the other cmake controlled projects. (Preferably
broken into
Brandon J. Van Every wrote:
John Biddiscombe wrote:
I've used boost a lot, but never spent much time looking at the
configuration or build. Has anyone given much though to how hard it'd
be to CMakeify Boost?
(And even if the boost maintainers aren't interested in using CMake,
we could put
Brandon
I'm not really interested in converting the boost maintainers to cmake.
I'm not at all interested in what they think about cmake (Political
buy-in is of no concern to me). I have cmakeified so many projects that
doing one more (even if it's quite a big one) doesn't put me off. (And I
