Hi,
In the libtool 2.2.4 relink command below, the ../../taglib/libtag.la
refers to a libtag.so library in the build directory. I'm, sorry about
the zillion compiler options, however I think only the -L options,
the ../../taglib/libtag.la and its corresponding
-L/var/tmp/pkgbuild-mwright/FOSStagl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've got a project where I'm building (by default) both shared and
static libraries using libtool. However, the shared library also exports
a java native interface, so I have a short list of .cpp files containing
JNI code that should be part of the sha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Calcote wrote:
> I've got a project where I'm building (by default) both shared and
> static libraries using libtool. However, the shared library also exports
> a java native interface, so I have a short list of .cpp files containing
> JNI code th
John Calcote wrote:
> Is there a way to specify additional objects (sources) for the shared
> library that will not be linked into the static library.
You could always wrap the entire contents of the file with "#ifdef
PIC". The objects would still be in the static lib but they would be
essential
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
Brian Dessent wrote:
> John Calcote wrote:
>
>> Is there a way to specify additional objects (sources) for the shared
>> library that will not be linked into the static library.
>
> You could always wrap the entire contents of the file with "
Hello Mark,
* Mark Wright wrote on Wed, Jun 11, 2008 at 04:17:11PM CEST:
>
> In the libtool 2.2.4 relink command below, the ../../taglib/libtag.la
> refers to a libtag.so library in the build directory. I'm, sorry about
> the zillion compiler options, however I think only the -L options,
> the .
