Re: [boost] bjam boost build on windows - changing the path strategy (stage)

Subject: Re: [boost] bjam boost build on windows - changing the path strategy (stage)
From: Robert (r.firl_at_[hidden])
Date: 2017-11-15 23:56:04

On 11/15/2017 2:54 PM, James E. King, III via Boost wrote:
> I would like to build boost into a prefix directory (.\b2.exe
> --prefix=C:\prefix) containing "C:\prefix\include\boost\..." and
> "C:\prefix\lib", just like the linux build does.  On Windows it builds into
> ""C:\prefix\include\boost-1_66\boost\..." instead - is there a bjam control
> to get rid of the version in the prefix include path for header copies?

I use a Windows environment variable to have the starting path set to 
whatever it needs to be.  In Visual Studio it is invoked by $(BOOST_INCLUDE)

For example:
BOOST_INCLUDE=C:\Boost\include\boost-1_63

Then, when 1.64 is built, the include variable becomes:
BOOST_INCLUDE=C:\Boost\include\boost-1_64

Visual Studio only reads environment variables when it first launches. 
Consequently, if it is already open, please restart it.

--Robert

> 
> - Jim
> 
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>