> -Original Message-
> From: Thomas Jahns [mailto:ja...@dkrz.de]
> Sent: Friday, March 06, 2015 1:46 AM
> To: Andy Falanga (afalanga)
> Cc: automake@gnu.org
> Subject: Re: How to use ld options correctly for --whole-archive in
> automake and libtool
>
> >&g
On 03/05/15 18:28, Andy Falanga (afalanga) wrote:
-Original Message-
From: Thomas Jahns [mailto:ja...@dkrz.de]
Sent: Wednesday, March 04, 2015 5:45 PM
To: Andy Falanga (afalanga)
Cc: automake@gnu.org
Subject: Re: How to use ld options correctly for --whole-archive in
automake and libtool
Hello Vincent,
On 03/05/15 18:43, Vincent Torri wrote:
I would also use $(top_builddir) instead of relative path. It could
help when building in another directory than the source one (like with
make distcheck)
I cannot see how .. would ever refer to the source tree and since libhwmgmt.la
is g
> -Original Message-
> From: Vincent Torri [mailto:vincent.to...@gmail.com]
> Sent: Thursday, March 05, 2015 1:26 PM
> To: Andy Falanga (afalanga)
> Cc: Thomas Jahns; automake@gnu.org
> Subject: Re: How to use ld options correctly for --whole-archive in
> automake an
>> Subject: Re: How to use ld options correctly for --whole-archive in
>> automake and libtool
>>
>> >
>> >> But what exactly is the problem with using e.g. ../Shared/HwMgmt/
>> >> libhwmgmt.la? That sata.so will then require libhwmgmt.so? libtool
>&
> -Original Message-
> From: Vincent Torri [mailto:vincent.to...@gmail.com]
> Sent: Thursday, March 05, 2015 10:44 AM
> To: Andy Falanga (afalanga)
> Cc: Thomas Jahns; automake@gnu.org
> Subject: Re: How to use ld options correctly for --whole-archive in
>
On 4 March 2015 at 19:05, Andy Falanga (afalanga) wrote:
> I'm trying to reproduce this using the automake tools. I have this in the
> Makefile.am located in sata:
>
> lib_LTLIBRARIES = satacpp.la
> satacpp_la_SOURCES = ...
>
> pyexec_LTLIBRAIRES = sata.la
> sata_la_LDFLAGS = -module
> sata_la_L
On Thu, Mar 5, 2015 at 6:28 PM, Andy Falanga (afalanga)
wrote:
>> -Original Message-
>> From: Thomas Jahns [mailto:ja...@dkrz.de]
>> Sent: Wednesday, March 04, 2015 5:45 PM
>> To: Andy Falanga (afalanga)
>> Cc: automake@gnu.org
>> Subject: Re: How to
> -Original Message-
> From: Thomas Jahns [mailto:ja...@dkrz.de]
> Sent: Wednesday, March 04, 2015 5:45 PM
> To: Andy Falanga (afalanga)
> Cc: automake@gnu.org
> Subject: Re: How to use ld options correctly for --whole-archive in
> automake and libtool
>
>
Hello Andy,
On Mar 4, 2015, at 20:05 , Andy Falanga (afalanga) wrote:
The team I work with has a project which is a C++ shared library
which is exposed in two different manners. The first is a
traditional C++ library and the second is it's exposed, through
Boost.python, as a module. I fou
Hi,
First of all, forgive my earlier e-mail of "Subscribe" to this. I was a bit
confused at the time reading the website. Now for the question.
The team I work with has a project which is a C++ shared library which is
exposed in two different manners. The first is a traditional C++ library a
11 matches
Mail list logo
