[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
different object sets in shared and static libs
From: |
John Calcote |
Subject: |
different object sets in shared and static libs |
Date: |
Wed, 11 Jun 2008 16:12:29 -0600 |
User-agent: |
Thunderbird 2.0.0.12 (X11/20080226) |
-----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 shared library, but has no business
in the static library.
Is there a way to specify additional objects (sources) for the shared
library that will not be linked into the static library.
I realize that linking these extra objects into the static library is
more or less benign, as no one will ever call these functions from the
static library, but it seems sad to carry the extra baggage in the
static library.
Thanks in advance,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIUE3NdcgqmRY/OH8RAs0dAJ9/v1i+Kxiw0nj/5OaF2SDgcUdgFQCePLE2
6ugOBlup8uthmMoa6ku7VMY=
=rq14
-----END PGP SIGNATURE-----
- different object sets in shared and static libs,
John Calcote <=