Re: [Boost-build] Working around boost-install rule limitations

From: Jonathan Biggar (jon_at_[hidden])
Date: 2008-06-15 10:36:48

Vladimir Prus wrote:
> On Sunday 15 June 2008 05:27:25 Jonathan Biggar wrote:
>> The boost-install rule only allows me to specify just the library 
>> projects to be installed, and takes care of the header files in 
>> boost/<libname> itself.  But this isn't adequate for my library, which 
>> pregenerates C++ header files that need to be installed in 
>> boost/<libname>, and also miscellaneous non-code library files that need 
>> to be installed in lib/<libname>/...
> 
> boost-install does not install anything in "lib/<libname>/..." -- all libraries
> go to "lib/...". Can you clarify what other non-code files you want to be
> installed? We sure can change boost-install to install extra things, but I
> suspect they should to to "share", not "lib".

Yes, "share" is a certain target too, certainly for source files that 
should be copied unchanged.  I also expect to have binary files 
generated by the build process but accessed read-only by the library, 
and those probably should be in "lib".

Looking further, I'll eventually need to place configuration files in 
"etc", and create subdirectories in "var" for runtime files.  That last 
is a bit more challenging, because on Linux, there's a "/var/local", but 
no "/usr/local/var".

On a slightly divergent topic, wouldn't it be better if the default 
install for boost on Unix variants was in "/opt/boost/" instead of 
"/usr/local"?  Boost isn't really local software.

-- 
Jon Biggar
Floorboard Software
jon_at_[hidden]
jon_at_[hidden]