On Thu, Feb 23, 2012 at 6:42 AM, Mandeville, Rob <rmandevi...@litle.com> wrote:
> Another possibility would be to put Boost in a non-standard location where
> autoconf/configure would never find it, install various versions of Boost
> that you need into various directories, and then pass command-line arguments
> to autoconf/configure specifying where to get your Boost library from.
We do this on windows where there is no "standard location" for boost.
We have a common mapped drive with several versions and the
developers can set a variable for which one they want. But now I'd
like to make a matrix build work across several versions of windows
and linux targets where one of the linux targets will have the
expected boost version installed natively but others will not. So
there are really two parts to the issue: first is it sane to even
build something against the wrong libs on linux, and second, how do
you map something in a matrix job to things that are location-specific
per node?
--
Les Mikesell
lesmikes...@gmail.com
