Re: [Boost-build] How can I avoid linking twice?

From: Kostas Kostiadis (kos_at_[hidden])
Date: 2007-01-05 10:17:56

Was there ever a known bug with this?
My timestamp.txt reads "Mon Nov 6 17:41:46 MSK 2006"

I've added in the top level project-root.jam

project	: requirements <hardcode-dll-paths>false ;

To make the dev one behave like the install one, but this had no effect.

I've tried the inverse, in the lower-level Jamfile, i.e. made my install
rule:

install executable : hello
        : <install-dependencies>on <install-type>EXE <location>./bin
<hardcode-dll-paths>true
        ;

And again this had no effect...(obviously I tried these one at a time ;-)).
Is there something wrong in my syntax somewhere?
Has anyone actualy done this in a unix/linux environment with success?

Thank you in advance,
Kos

-----Original Message-----
From: boost-build-bounces_at_[hidden]
[mailto:boost-build-bounces_at_[hidden]] On Behalf Of Vladimir Prus
Sent: 20 December 2006 20:00
To: boost-build_at_[hidden]
Subject: Re: [Boost-build] How can I avoid linking twice?

On Wednesday 20 December 2006 19:21, Kostas Kostiadis wrote:
> Hello all,
> 
> I have a project, with an "output" directory for all intermediate files
and
> a "bin" directory for the executables.
> What seems to happen is that my app gets linked twice...once so that the
> executable goes into "output" and once during the install so that the
> executable goes to "bin".

The bins in 'output' are built with <hardcode-dll-paths>true, since that's
good for development.

The install rule uses <hardcode-dll-paths>false, since that's better for
deployment. So, either add <hardcode-dll-paths>true to requirements
of your install target, or use <hardcode-dll-paths> as top-level
project requirement.

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