[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: Ralf Wildenhues
Subject: Re: Questions on exporting functions from a shared library
Date: Wed, 8 Oct 2008 23:42:18 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

* 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

>>> 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:

> 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:


reply via email to

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