Re: boost.build outside the boost directory

On Wednesday 22 August 2007 12:01:26 Thorsten Ottosen
wrote:
> Hi Vladimir,
> 
> I was hoping you could help me out a bit with bjam.

Hi Thorsten,
please direct all Boost.Build questions to the
boost-buildlists.boost.org
mailing list, where you'll get help from more persons and
where
any answers will benefit new users.

I CC the list, please reply to the list.

> I'm getting a warning
> 
>
D:/boost/trunk/tools/build/v2/buildvirtual-target.jam:996:
in 
> virtual-target.re
> gister-actual-name from module virtual-target
> error: Duplicate name of actual target: 
> <pbinmsvc-8.0debugthreading-multi>bay
> esian.lib

Well, is this a *complete* error message? I'm pretty
sure it is not, and the part you've trimmed out
contains important information -- how the conflicting
targets differ in properties.

> in my project. I can run normal boost unit-test inside
the boost 
> repository, but I'm now using bjam in a non-boost
related project.
>   There was a FAQ entry about this in the new
documentation, but that is 
> not the reason here. Maybe you can see the problem by
looking at my Jamfile?
> 
> In the above warning, I don't get why it says
"threading-multi", because 
> I only want to build a static library.

Because msvc-8.0 cannot create single-threaded code. The
problem you
see can be possibly related to this, but I need full output
to be sure.
So, please run again and send me the full output. Also, add
the
--debug-building option to bjam invocation -- this will
provide some extra
information.

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus skrev:
 > On Wednesday 22 August 2007 12:01:26 Thorsten Ottosen
wrote:
 >> Hi Vladimir,
 >>
 >> I was hoping you could help me out a bit with
bjam.
 >
 > Hi Thorsten,
 > please direct all Boost.Build questions to the 
boost-buildlists.boost.org
 > mailing list, where you'll get help from more persons
and where
 > any answers will benefit new users.
 >
 > I CC the list, please reply to the list.

Sorry for that. I'll use this list from know on.

 >> I'm getting a warning
 >>
 >>
D:/boost/trunk/tools/build/v2/buildvirtual-target.jam:996:
in 
virtual-target.re
 >> gister-actual-name from module virtual-target
 >> error: Duplicate name of actual target: 
<pbinmsvc-8.0debugthreading-multi>bay
 >> esian.lib
 >
 > Well, is this a *complete* error message? I'm pretty
 > sure it is not, and the part you've trimmed out
 > contains important information -- how the conflicting
 > targets differ in properties.

You're right it is not the complete message.

 >> in my project. I can run normal boost unit-test
inside the boost 
repository, but I'm now using bjam in a non-boost related
project.
 >>   There was a FAQ entry about this in the new
documentation, but 
that is not the reason here. Maybe you can see the problem
by looking at 
my Jamfile?
 >>
 >> In the above warning, I don't get why it says
"threading-multi", 
because I only want to build a static library.
 >
 > Because msvc-8.0 cannot create single-threaded code.

Wow. Didn't know that.

 > The problem you
 > see can be possibly related to this, but I need full
output to be sure.
 > So, please run again and send me the full output.
Also, add the
 > --debug-building option to bjam invocation -- this
will provide some 
extra
 > information.

Yes. Here's the new output as an attachment.

I tried changing threading to multi, but it did not have an
impact AFAICT.

best regards

-Thorsten

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus skrev:
> On Wednesday 22 August 2007 12:01:26 Thorsten Ottosen
wrote:

>> in my project. I can run normal boost unit-test
inside the boost 
>> repository, but I'm now using bjam in a non-boost
related project.
>>   There was a FAQ entry about this in the new
documentation, but that is 
>> not the reason here. Maybe you can see the problem
by looking at my Jamfile?

I have messed a bit around with my settings of BOOST_ROOT
and 
BOOST_BUILD_PATH.

Bjam starts to work when I set BOOST_BUILD_PATH to point to
the version 
from 1.34.0 (I had this version lying around). So it seems
that it must 
be a fairly recent change that has broken the property.

I'm not good at reading bjam files yet, but let my know what
I can do to 
help nail this one down. Till then, I'll use the 1.34
version of the rules.

best regards

Thorsten


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus skrev:

>> in my project. I can run normal boost unit-test
inside the boost 
>> repository, but I'm now using bjam in a non-boost
related project.
>>   There was a FAQ entry about this in the new
documentation, but that is 
>> not the reason here. Maybe you can see the problem
by looking at my Jamfile?

I got my setup to work.

What I did was to point BOOST_BUILD_PATH to v2 in the 1.34
distribution 
instead of the subversion version.

Let me know if I can do something to help track this down.

best regards

-Thorsten
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build