Vincent Torri wrote:
On Wed, 4 Jun 2008, Ralf Wildenhues wrote:
* Vikram Ambrose wrote on Wed, Jun 04, 2008 at 03:54:35PM CEST:
However I need to pass separate CPPFLAGS to the objects destined for the
shared library as opposed to the objects destined for the library
archive.
As Andreas al
On Wed, 4 Jun 2008, Ralf Wildenhues wrote:
* Vikram Ambrose wrote on Wed, Jun 04, 2008 at 03:54:35PM CEST:
However I need to pass separate CPPFLAGS to the objects destined for the
shared library as opposed to the objects destined for the library
archive.
As Andreas already replied, just us
* Vikram Ambrose wrote on Wed, Jun 04, 2008 at 03:54:35PM CEST:
>
> However I need to pass separate CPPFLAGS to the objects destined for the
> shared library as opposed to the objects destined for the library
> archive.
As Andreas already replied, just use "#ifdef PIC" for shared and
"#ifndef P
Vikram Ambrose <[EMAIL PROTECTED]> writes:
> Andreas Schwab wrote:
>> Vikram Ambrose <[EMAIL PROTECTED]> writes:
>>
>>
>>> Can someone suggest a way I can produce both a static and shared library
>>> with libtool/autoconf/automake that are compiled with different CPPFLAGS?
>>>
>>
>> You ca
Andreas Schwab wrote:
Vikram Ambrose <[EMAIL PROTECTED]> writes:
Can someone suggest a way I can produce both a static and shared library
with libtool/autoconf/automake that are compiled with different CPPFLAGS?
You can use #ifdef PIC.
Andreas.
I looked up fpic and fPIC in the gc
Vikram Ambrose <[EMAIL PROTECTED]> writes:
> Can someone suggest a way I can produce both a static and shared library
> with libtool/autoconf/automake that are compiled with different CPPFLAGS?
You can use #ifdef PIC.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products
Dear All,
I have some code that I am trying to build with the aid of libtool,
autoconf and automake. I require both a static and shared library of my
code, and libtool provides this functionality beautifully.
However I need to pass separate CPPFLAGS to the objects destined for the
shared lib
