|
Boost : |
From: David Abrahams (dave_at_[hidden])
Date: 2004-09-03 13:34:35
Richard Hadsell <hadsell_at_[hidden]> writes:
> David Abrahams wrote:
>
>>Use tools/build/v1/gcc-tools.jam as a working example and
>>tools/build/v1/gcc-tools.html to understand it.
>>
>>See
>>http://www.boost.org/tools/build/v1/build_system.htm#toolset_description
>>for other help.
>>
>>
> Thanks for the help. I have made some progress at creating a
> pathscale-tools.jam, starting from mipspro-tools.jam (but keeping my
> eye on gcc-tools.jam, in case of link problems).
>
> I can't figure out a couple of things about the output. Due to
> compiler problems I haven't finished a build, but I can see that the
> output files in the stage directory are being named this way:
>
> libboost_date_time-pathscale-1_31.a
>
> When building for the intel-linux toolset, I see 2 copies of the
> equivalent file:
>
> libboost_date_time-il-1_31.a
> libboost_date_time-il.a
>
> I would like to know (a) how to abbreviate 'pathscale' to 'ps' in the
> file names and (b) how to make a second copy of each file without the
> Boost version in the name. (Perhaps (b) will take care of itself, if
> the build ever finishes successfully.)
I got this from Rene, who knows:
attached mail follows:
Dave,
Could send this along, I don't have access to the Boost list right now...
(a) You need to change the rule common-variant-tag in boost-base.jam.
(b) Yes, the unversioned files will be taken care of at the end of the build.
--grafik
HTH,
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk