Boost logo

Boost :

Subject: Re: [boost] building, debugging and contributing to an individual boost library
From: John Maddock (jz.maddock_at_[hidden])
Date: 2019-02-17 15:31:50

> 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).  Every so often you will get a library which depends
on the develop branch of something else, but that's not too common.  You
can always clone boost-master, and switch individual sub-libraries to
develop if you hit that particular case.

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 ;)

HTH, John.

This email has been checked for viruses by Avast antivirus software.

Boost list run by bdawes at, gregod at, cpdaniel at, john at