-- Dan Timis wrote:
>Is there any way to export only the functions that are called by the
>code we link to, without exposing the internal workings? Ideally we
>would like to be able to provide a static library created with ar or
>ranlib, link that library with other object files to create a .ex
From: Mike Hearn <[EMAIL PROTECTED]>
Subject: Re: Exporting symbols
Date: Thu, 13 May 2004 10:39:42 +0100
Organization: CodeWeavers, Inc
On Wed, 12 May 2004 19:45:42 -0700, Dan Timis wrote:
After running strip on the .exe.so if we do nm -D all the symbols are
still there. Is there any way
On Wed, 12 May 2004 19:45:42 -0700, Dan Timis wrote:
> After running strip on the .exe.so if we do nm -D all the symbols are
> still there. Is there any way to get rid of the ones that are not
> needed for dynamic linking?
Dmitry is right, ask on the binutils list. However if you hide symbols
u
"Dan Timis" <[EMAIL PROTECTED]> wrote:
> I'm really, really sorry for this. I should have done my research
> first.
>
> After running strip on the .exe.so if we do nm -D all the symbols are
> still there. Is there any way to get rid of the ones that are not
> needed for dynamic linking?
Act
I'm really, really sorry for this. I should have done my research
first.
After running strip on the .exe.so if we do nm -D all the symbols are
still there. Is there any way to get rid of the ones that are not
needed for dynamic linking?
Thanks,
Dan
On Wednesday, May 12, 2004, at 05:43 PM,
Oops. I misspoke.
I was relating what a colleague told me. After I sent the message I
thought I would try it myself (I should have tried before). Running
"strip" does remove the symbols and running "nm" after that does not
show any symbols.
My colleague clarified the problem. After running
Hi,
We need to have a library that links statically to a wine application.
The wine application is an .exe.so, so everything becomes in the end an
exe.so. The problem we have is that all the symbols are exposed.
I have very little experience with Windows, but I understand that with
a Windows
