Edward Diener wrote: First off... This documentation is being worked on. Thankfully not by me, as I make a bad documenter in this case since I wrote the install support.
The documentation for building Boost states that one can use 'install', 'stage', or nothing on the bjam command line. But it does not explain the difference between these options other than:
"none Only builds the Boost libraries. This lets you do the first part of what the install action normally does without copying the built libraries to the install location.
install Builds and installs Boost libraries and headers.
stage Builds the Boost libraries and copies them into a common directory."
This tells me almost nothing. In the 'none' explanation, what does "copying the built libraries to the install location" mean when the install location is never specified ?
It's the standard, by autoconf POV, definition, and is the location specified by "--prefix=*" option.
In the 'install' explanation, what does "installs Boost libraries and headers" mean and why do headers need to be installed ?
It mean it will copy the built libraries, and all the headers for all the Boost libraries. Especially important as most of the Boost libraries are header only.
In the 'stage' explanation, what is the "common directory" to which Boost libraries are copied ?
It's the directory specified by "--stagedir=*" option, which defaults to "./stage". I.e. a "stage" directory where you unpacked the Boost sources.
In general where exactly are resulting libraries put for each of these options and are header files moved anywhere also ?
See above :-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org