Boost logo

Boost-Build :

Subject: Re: [Boost-build] building the final library name...
From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2010-01-19 07:12:46

Thomas Lehmann wrote:
> Hi!
> Am 19.01.2010 10:07, schrieb Juergen Hunold:
>> Hi !
>> On Tuesday 19 January 2010, you wrote:
>>> Of course. Here's the hello world example: (attachment)
>>> One Jamroot and a helloWorld.cxx file.
>>> I'm getting a helloWorld.exe only.
>> Please try the attached one.
>> I think the main culprit was that "<tag>" must be specified at
>> project level. And if you use "<toolset>" you can get rid of the
>> multiple exe declaration unless you have different sources for the
>> platforms.
> Does still not produce other than helloWorld.exe!

Works for me (after adding a dummy main.cxx file):

>set HOSTNAME=TheHost
>bjam -q
warning: No toolsets are configured.
warning: Configuring default toolset "msvc".
warning: If the default is wrong, your build may not work correctly.
warning: Use the "toolset=xxxxx" option to override our guess.
warning: For more configuration options, please consult
...found 16 targets...
...updating 5 targets...
compile-c-c++ bin\TheHost\helloWorld\msvc-9.0\debug\main-vc90.obj
main.cxx bin\TheHost\helloWorld\msvc-9.0\debug\helloWorld-vc90.exe
msvc.manifest bin\TheHost\helloWorld\msvc-9.0\debug\helloWorld-vc90.exe
common.copy ..\Binaries\TheHost\helloWorld-vc90.exe
        1 file(s) copied.
common.copy ..\Binaries\TheHost\helloWorld-vc90.pdb
        1 file(s) copied.
...updated 5 targets...

"bjam --version" gives:

Boost.Build V2 (Milestone 12)
Boost.Jam 3.1.18

A small caveat though: It seems to be neccesary to specify the
"address-model" and "target-os" options explicitly on the command-line in
order to have them included properly in the tagged names. As you can see
above, only the compiler tag is included.

If you try the exact file that Juergen provided, does it still not work?

Regards / Johan

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at