[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Questions on exporting functions from a shared library

From: Jef Driesen
Subject: Re: Questions on exporting functions from a shared library
Date: Thu, 09 Oct 2008 17:26:46 +0200
User-agent: Thunderbird (Windows/20080914)

Ralf Wildenhues wrote:
* Jef Driesen wrote on Wed, Oct 08, 2008 at 10:24:46AM CEST:
I am shipping the symbols file. In my, I have

EXTRA_DIST = mylib.symbol

to make sure the file is included in the tarball.

But with this approach, msvc users will need to (manually) generate a DEF file from it. And that is something I would like to avoid.

Hmm.  I suppose shipping the DEF file for them (for one setup?) won't

Shipping a DEF file matching the default features would be a possibility. But if someone wants to enable/disable some features, they'll have to modify that file, and I have to make sure I always update both the symbols and DEF file.

Note: How do can I detect whether the visibility attribute is supported?
For example with the gnulib module 'visibility'.
How do I use this visibility.m4 file? Do I need to copy its contents into my file?

No, you ship it additionally; see the AC_CONFIG_MACRO_DIR description here:

Typically, you just import the whole gnulib module:

I'll have a look at that.

BTW, what is the reason that when I use mylib_la_CFLAGS = -DMYLIB_BUILD, in, all my object files are named "mylib_la-myfile.o" instead of the regular "myfile.o"?

Addressed here:

I was already thinking in that direction, but since there is only one target that needs to be build in my case, there is no need to rename object files and I assumed automake would not rename. That's why I curious whether there was another reason that could cause this.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]