Boost logo

Boost-Build :

From: Norbert Unterberg (nunterberg_at_[hidden])
Date: 2007-01-24 16:49:11


Vladimir Prus schrieb:
> On Wednesday 24 January 2007 18:57, Norbert Unterberg wrote:
>> Volodya,
>>
>>> We have internal mechanism to handle build-os != target-os, but nobody
>>> used it so far, so no wonder that gcc or shared library might be still
>>> looking at build os. Just report the particular issues you run into
>>> and I'll try to address them when I get back home on Monday.
>> Any new information on this issue? Is there a command line switch to
>> force bjam to a particular target-os? I have searched the list archive
>> on gmane for "target-os" but only found some mailings about using a
>> <targer-os> feature inside of jam files. Can you give us some help?
>
> Ah, to begin with, it turns out that you're using Boost.Build V1. I kinda assumed that you're
> using V2. I'd suggest to obtain CVS version of Boost (preferrably RC_1_34_0 branch),
> and try it. V1 is kinda unsupported at this time.

Thank you for taking the time to help me.

I am confused. All I wanted to do is to build the current official boost library
(which is 1.33.1 I guess). To do that, I downloaded boost 1.33.1 and boost-jam.
I do not know about boost.build. I thought that the boost archive contains
everything to build the boost libraries. Or is boost.build v2 included in
rc_1_34_0 so that you suggest using that version?

When will boost 1.34 be released? Is it stable to use it in a production
environment?

I am sorry, I thought I could download boost, compile it and start using it im
my project, without spending a week learning the internals of its build system...

To answer your question in your other mail, I did not build bjam, I used the
windows binary. This is because the getting starting guide suggests you just
need a running bjam executable, no matter which one, and bjam automatically
detects the build environment.

As I said, a colleague of mine did build bjam under cygwin and he managed to
build boost, but he did get cygwin DLL files instead of linux shared libraries.
That's why I keep asking for the magic switch ;-) to tell bjam we have a LINUX
target created under a CYGWIN host.

We have cross-compiled another library, and all we did there was running
./configure -host x86-486-linux-gnu, and all went well. But what is the
corresponding option for bjam?

Norbert


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