* Vikram Ambrose wrote on Tue, Jul 22, 2008 at 03:22:09PM CEST:
> Ralf Wildenhues wrote:
>> * Vikram Ambrose wrote on Mon, Jul 21, 2008 at 11:36:25PM CEST:
>>
>>> Just ran into a problem, with our old solution, both the .a and the
>>> .so need to have -fPIC. Now how do i get separate CPPFLAGS
Ralf Wildenhues wrote:
Hello Vikram,
* Vikram Ambrose wrote on Mon, Jul 21, 2008 at 11:36:25PM CEST:
Just ran into a problem, with our old solution, both the .a and the .so
need to have -fPIC. Now how do i get separate CPPFLAGS to them when
using libtool?
You should be looking into
Hello Vikram,
* Vikram Ambrose wrote on Mon, Jul 21, 2008 at 11:36:25PM CEST:
> Just ran into a problem, with our old solution, both the .a and the .so
> need to have -fPIC. Now how do i get separate CPPFLAGS to them when
> using libtool?
You should be looking into convenience archives, or, i
Vikram Ambrose wrote:
Ralf Wildenhues wrote:
* Vikram Ambrose wrote on Thu, Jun 05, 2008 at 03:59:38PM CEST:
Thanks all. However modifying the code is not a possibility. I do
understand that the code is not designed properly. I am looking for a
way to configure the build tools to
Ralf Wildenhues wrote:
* Vikram Ambrose wrote on Thu, Jun 05, 2008 at 03:59:38PM CEST:
Thanks all. However modifying the code is not a possibility. I do
understand that the code is not designed properly. I am looking for a
way to configure the build tools to build the code properly instead
* Vikram Ambrose wrote on Thu, Jun 05, 2008 at 03:59:38PM CEST:
> Thanks all. However modifying the code is not a possibility. I do
> understand that the code is not designed properly. I am looking for a
> way to configure the build tools to build the code properly instead of
> configuring th
Roumen Petrov wrote:
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
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
13 matches
Mail list logo
