On Mon, Apr 04, 2011 at 10:24:54PM +0200, Olaf van der Spek wrote:
> On 31-3-2011 2:56, Steve M. Robbins wrote:
> >My understanding of the use-case is: suppose you are using
> >Boost.Build to build a project that contains a library
> >as well as an executable linked with that lib. If the
> >librar
On 31-3-2011 2:56, Steve M. Robbins wrote:
My understanding of the use-case is: suppose you are using
Boost.Build to build a project that contains a library
as well as an executable linked with that lib. If the
library is built as a shared object, the hardcode-dll-paths
lets you build and run th
Hi,
Thanks Steve, I agree with your explanation. For further information, this
use-case is mentionned as useful here, in the second paragraph:
http://www.boost.org/boost-build2/doc/html/bbv2/faq/dll-path.html
When developping, especially if you have a fairly large number of libraries
(about
Hi,
On Tue, Mar 29, 2011 at 03:12:31PM +0200, Olaf van der Spek wrote:
> > This feature is really useful for developpers.
>
> Why?
My understanding of the use-case is: suppose you are using
Boost.Build to build a project that contains a library
as well as an executable linked with that lib. If
> This feature is really useful for developpers.
Why?
Olaf
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: libboost1.46-dev
Version: 1.46.1-3
Severity: important
Hi,
Since boost-build is provided by libboost1.46-dev, the hardcode-dll-paths
feature is missing. This means that executables built using Boost.Build do not
include anymore the absolute paths to the dll libraries. This feature is rea
6 matches
Mail list logo
