|
Boost-Build : |
Subject: Re: [Boost-build] [boost] User config commands needed to find Clang tools ar and ranlib
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2012-11-20 11:44:50
> > -----Original Message-----
> > From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]] On Behalf Of Paul A.
> > Bristow
> > Sent: Monday, November 19, 2012 1:10 PM
> > To: boost_at_[hidden]
> > Subject: [boost] User config commands needed to find Clang tools ar
> > and ranlib
> >
> > I am trying to use the Clang compiler to build a Boost.Test library
> > and have now found the necessary user- config.jam to select the compiler (thanks Jurgen Hunold)
, but
> the link stage tools are not being found.
> >
> > Can anyone suggest what bjam incantation is needed ?
> >
> > Thanks
> >
> > Paul
> >
> > clang-linux.archive
> > i:\boost-trunk\boost\bin.v2\libs\test\build\clang-linux-3.1\debug\link
> > -static\runtime-link-static\th
> > reading-multi\libboost_prg_exec_monitor-clang31-mt-sd-1_53.lib
> > '"ar"' is not recognized as an internal or external command, operable program or batch file.
> > '"ranlib"' is not recognized as an internal or external command, operable program or batch file.
> >
> > "ar" rc
> > "i:\boost-trunk\boost\bin.v2\libs\test\build\clang-linux-3.1\debug\lin
> > k-static\runtime-link-static\t
> > hreading-multi\libboost_prg_exec_monitor-clang31-mt-sd-1_53.lib"
> > "i:\boost-trunk\boost\bin.v2\libs\test\build\clang-linux-3.1\debug\lin
> > k-static\runtime-link-static\t
> > hreading-multi\execution_monitor.obj"
> > "i:\boost-trunk\boost\bin.v2\libs\test\build\clang-linux-3.1\debug\lin
> > k-static\runtime-link-static\t
> > hreading-multi\debug.obj"
> > "i:\boost-trunk\boost\bin.v2\libs\test\build\clang-linux-3.1\debug\lin
> > k-static\runtime-link-static\t
> > hreading-multi\cpp_main.obj"
> > "ranlib"
> > "i:\boost-trunk\boost\bin.v2\libs\test\build\clang-linux-3.1\debug\lin
> > k-static\runtime-link-static\t
> > hreading-multi\libboost_prg_exec_monitor-clang31-mt-sd-1_53.lib"
> >
> > ...failed clang-linux.archive
> > i:\boost-trunk\boost\bin.v2\libs\test\build\clang-linux-3.1\debug\link
> > -static\runtime-link-static\th
> > reading-multi\libboost_prg_exec_monitor-clang31-mt-sd-1_53.lib...
> >
> > My user-config.jam contains
> >
> > using clang
> > : #version
> > 3.1
> > : # compiler
> > "C:/mingw32-dw2/bin/clang++.exe"
> > #"C:/mingw32-dw2/bin/ar.exe" <<<< actual locations of tools
> > #"C:/mingw32-dw2/bin/ranlib.exe" <<<< actual locations of tools
> > : # options
> > <cxxflags>-v # verbose for testing.
> > <cxxflags>-IC:/mingw32-dw2/include/c++/4.6.3 # for stdlib?
> > #e:/dev/apps/mingw64/include/c++/4.7.2
> > <cxxflags>-IC:/mingw32-dw2/i686-w64-mingw32/include
> > #e:/dev/apps/mingw64/include/c++/4.7.2/x86_64-w64-mingw32
> > # <cxxflags>-std="c++11"
> > <root>"C:/mingw32-dw2/bin" # attempt to find the link tools
> > ;
I have hacked this by adding
set PATH=c:/mingw32-dw2/bin;%PATH%
to the command file that calls bjam.
This allows the toolset to find the programs ar.exe and ranlib.exe (which is the same as the
clang++.exe location).
But this can't be the 'right' way to do this can it?
<root>"C:/mingw32-dw2/bin" # attempt to find the link tools doesn't work as I expected.
Surely I should add their location/path info to the toolset?
using clang ...
????
Thanks
Paul
> > ---
> > Paul A. Bristow,
> > Prizet Farmhouse, Kendal LA8 8AB UK
> > +44 1539 561830 07714330204
> > pbristow_at_[hidden]
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