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: Peter Dimov (lists_at_[hidden])
Date: 2017-11-16 01:57:05

James E. King, III wrote:

> I am asking for a way for bjam to remove boost-1_66 in the path to the 
> include during the install job because I am going to package up include/ 
> and lib/ into a jfrog repository for a gradle build system. I guess I will 
> just move include/boost-1_66/boost into include/boost and then package it, 
> then move it back so that I can build again incrementally.

The reason there's boost-1_66 in the include directory on Windows is (I 
surmise) so that you can install more than one Boost version side by side. 
Since the version is encoded into the names of the libraries, they can share 
a single directory, but headers cannot.