Re: Re: Avoid deleting (pre-built) dependencies on clean

From: Johan Nilsson (r.johan.nilsson_at_[hidden])
Date: 2005-06-01 02:20:29

"Vladimir Prus" <ghost_at_[hidden]> wrote in message 
news:200505311925.33923.ghost_at_cs.msu.su...
> On Friday 20 May 2005 11:12, judoka1981 wrote:
>
>> > root/Jamfile. I'm using the install rule as I'd like all libraries
>> > (pre-built as well as included in project) at the same location.
>>
>> Just wanted to add that the install rule also tries to copy
>> prebuilt.lib onto itself, even though "<install-dependencies>off" is
>> specified.
>
> "Onto itself"? That's very stange. I've tried with this Jamfile:
>
> lib prebuilt : : <file>libprebuilt.a ;
> lib my : my.cpp prebuilt ;
> install dist : my ;

I've got a subdir called "libs", which is supposed to contain prebuilt _and_ 
generated libraries. After building e.g. "my" lib I try to install it into 
"libs", where the prebuilt is already located, hence the attempt to specify 
<install-dependencies>off.

Does that explain the problem better to you?

>
> When built with "bjam -n link=static", it would try to copy 
> "libprebuilt.a" to
> "dist", which is more or less expected.

Unless <install-dependencies>off, or?

>
> The explanation is that when 'my' is built as static library, it can 
> directly
> link to 'prebuilt'. So, all targets using 'my' will implicitly use 
> 'prebuilt'.
> If you had:
>
> exe main : main.cpp my ;
>
> that would be OK. For 'install' rule, that's less nice. I can try fixing 
> that,
> but first we need to figure out why in your case, prebuilt is copied onto
> itself.

See above.

HTH // Johan