From: John Maddock (jz.maddock_at_[hidden])
Date: 2019-11-03 13:08:44
On 03/11/2019 06:22, ERR ORR via Boost-build wrote:
> I am writing for help building V1.71 and additional modules Asio,
> Checking the log output, the build tool appears to not build these
> modules by default.
> Secondly, the build tool appears to not be documented correctly.
> >From perusing Stack Overflow, it appears that I'm not the only one
> w/this problem.
> I would be grateful if somebody could answer me some questions:
> - Why does Boost not use the classic ./configure/make/make INSTALL
> build sequence? On top of that, the "jam" tool which Boost uses
> appears to be documented incorrectly (I can read english beyond
> school grade in case thats an issue).
To repeat, a configure script with msvc is about as useful as a bicycle
is to a fish.
> - Could someone please explain to me how I build exactly ONE
> additional module, for example Asio?
From the root directory:
Will build "libraryname"
You would have discovered that with a :
But.... Asio is header only, there *so is nothing to build*, likewise
> - Could somebody please explain to me how I can build the whole
> library, module by module, dependably, to <stage>, if must be,
> and from there to the <INSTALL> destination?
Will build everything.
> - Could somebody please explain to me why Boost has decided to NOT
> include certain modules in default build process, and how do I circumvent this?
It *does* include everything that needs building in the default build
> - What is a .JAM file for? search sez game and audio software, I think
> of marmalade.
The build script.
> Lastly, the non-sequitur about windows installation which I received after my
> last attempt is artless.
> Thank you for any help/guidance,
> Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk