Subject: Re: [boost] building, debugging and contributing to an individual boost library
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2019-02-17 17:48:08
On Sun, 17 Feb 2019 at 16:31, John Maddock via Boost
> > FYI, some libraries allow 'lightweight' development setup: clone only
> > library you want to contribute to and test it using Boost libraries
> > installed from (fairly recent) release package.
> For "casual" development that's by far the best way: clone the
> individual library you want to contribute to, and just place it's
> include directory before the boost-wide include path on the command line
> (or in your IDE).
I'm glad to have the workflow confirmed as reasonable
and not a whim :)
> There are also very few Boost libraries that require any special
> handling when building even if they're not header only, so I have a
> visual studio solution I call "libraries" with one sub-project in it for
> each library that has separate source files (or at least those I
> actually need) - I build these as static libraries with BOOST_ALL_NO_LIB
> defined for each project to disable auto-linking. Then I have one
> project solution for each library I want to work on, and import into
> that whatever other library-projects I need on an ad-hoc basis.
> Hopefully that makes sense ;)
I have used CMake to achieve purpose.
-- Mateusz Loskot, http://mateusz.loskot.net
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk