[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with cross build for windows on linux with shared libraries
From: |
Nikos Mavrogiannopoulos |
Subject: |
Re: Problem with cross build for windows on linux with shared libraries |
Date: |
Mon, 09 Sep 2013 11:59:44 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7 |
On 09/05/2013 08:46 PM, B. Scott Michel wrote:
> ".def" symbol export files should be avoided, if at all possible. Use
> the '.dll.a' archives -- libtool ensures that the '.dll.a' files are
> properly generated.
>
> However, this requires that the gnutls library do two things: (a) use
> symbol visibility attributes in the code to mark imported/exported
> functions, (b) arrange for the "right" symbol visibility when compiling
> the library vs. compiling non-library/application code. For the WinXX
> platform, import vs. export preprocessor header file management isn't
> complicated, but can be messy. There is a subtle benefit for the Linux
> and shared object platforms: gnutls can hide symbols and generally speed
> up dynamic linking (as opposed to making all symbols visible, which is
> the default.)
Hello,
We use the gnu ld script option to specify the exported symbols. Isn't
this information being used in the windows platform?
regards,
Nikos