This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: Limiting the exported symols in a shared library
- From: Moshe Libenson <liben_nm at netvision dot net dot il>
- To: gcc-help at gcc dot gnu dot org
- Date: Fri, 11 Oct 2002 22:49:49 +0200
- Subject: RE: Limiting the exported symols in a shared library
For the GNU linker it's --version-script
Read about it hear
http://www.gnu.org/manual/ld-2.9.1/html_mono/ld.html#SEC25
Moshe Libenson
moshe@libenson.org
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Barry Leslie
Sent: Friday, October 11, 2002 9:16 PM
To: gcc-help@gcc.gnu.org
Subject: Limiting the exported symols in a shared library
Hi,
I want to create a shared lib and limit the symbols exported from it to
the
functions specified in an api list. I don't want all the global symbols
to
be visible.
On many platforms this is done simply by listing the symbols in a file
and
then passing the file name in as a command line argument. For example on
AIX
you use -bE:api.exports and on Sun you use -M api.exports.
What is the equivalent for the linker on Linux?
I tried --retain-symbols-file api.exports but all the global variables
and
functions were still visible when I did a 'nm -g mylib.so'.
Can anybody help me out here?
Thanks,
Barry