Re: Questions on exporting functions from a shared library

2008-10-09 Thread Ralf Wildenhues
* Jef Driesen wrote on Thu, Oct 09, 2008 at 05:26:46PM CEST: > Ralf Wildenhues wrote: >> * Jef Driesen wrote on Wed, Oct 08, 2008 at 10:24:46AM CEST: >>> BTW, what is the reason that when I use mylib_la_CFLAGS = >>> -DMYLIB_BUILD, in Makefile.am, all my object files are named >>> "mylib_la-myfil

Re: Questions on exporting functions from a shared library

2008-10-09 Thread Jef Driesen
Ralf Wildenhues wrote: * Jef Driesen wrote on Wed, Oct 08, 2008 at 10:24:46AM CEST: I am shipping the symbols file. In my Makefile.am, 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

Re: Questions on exporting functions from a shared library

2008-10-08 Thread Ralf Wildenhues
* Jef Driesen wrote on Wed, Oct 08, 2008 at 10:24:46AM CEST: > > I am shipping the symbols file. In my Makefile.am, 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

Re: Questions on exporting functions from a shared library

2008-10-08 Thread Jef Driesen
Ralf Wildenhues wrote: * Jef Driesen wrote on Thu, Oct 02, 2008 at 05:08:55PM CEST: mylib.exp: mylib.symbols if XYZ $(CPP) -P -DMYLIB_XYZ_SUPPORT - < mylib.symbols | sed -e '/^$$/d' > $@ else $(CPP) -P - < mylib.symbols | sed -e '/^$$/d' > $@ endif CLEANFILES = mylib.exp EXTRA_DIST = mylib.

Re: Questions on exporting functions from a shared library

2008-10-05 Thread Ralf Wildenhues
* Jef Driesen wrote on Thu, Oct 02, 2008 at 05:08:55PM CEST: > > mylib.exp: mylib.symbols > if XYZ > $(CPP) -P -DMYLIB_XYZ_SUPPORT - < mylib.symbols | sed -e '/^$$/d' > $@ > else > $(CPP) -P - < mylib.symbols | sed -e '/^$$/d' > $@ > endif > > CLEANFILES = mylib.exp > EXTRA_DIST = mylib.symbol

Re: Questions on exporting functions from a shared library

2008-10-02 Thread Jef Driesen
Ralf Wildenhues wrote: Hello Jef, * Jef Driesen wrote on Tue, Sep 23, 2008 at 08:44:47PM CEST: Brian Dessent wrote: There are two aspects to the symbol visibility stuff: [ snip nice explanation ] Now that I start to understand all the differences, I only need to find a way how to incorpora

Re: Questions on exporting functions from a shared library

2008-10-01 Thread Ralf Wildenhues
Hello Jef, * Jef Driesen wrote on Tue, Sep 23, 2008 at 08:44:47PM CEST: > Brian Dessent wrote: >> There are two aspects to the symbol visibility stuff: [ snip nice explanation ] > Now that I start to understand all the differences, I only need to find > a way how to incorporate everything nicel

Re: Questions on exporting functions from a shared library

2008-09-23 Thread Jef Driesen
Brian Dessent wrote: Jef Driesen wrote: And how about gcc < 4.0 that do not support the visibility attributes? Is there a way to hide non-public symbols? Is the version script still available in this case? Is it possible to use both the attributes and the -export-symbols together? There are t

Re: Questions on exporting functions from a shared library

2008-09-22 Thread Brian Dessent
Jef Driesen wrote: > And how about gcc < 4.0 that do not support the visibility attributes? > Is there a way to hide non-public symbols? Is the version script still > available in this case? Is it possible to use both the attributes and > the -export-symbols together? There are two aspects to the

Re: Questions on exporting functions from a shared library

2008-09-22 Thread Jef Driesen
Brian Dessent wrote: Jef Driesen wrote: The MSDN documentation [1] about this issue, gives me the impression that applications have to relink when new symbols are added to the library (when not using a DEF). And that's something I would like to avoid. Actually this statement surprises me, so I'

Re: Questions on exporting functions from a shared library

2008-09-19 Thread Ralf Wildenhues
* Brian Dessent wrote on Fri, Sep 19, 2008 at 05:18:08PM CEST: > Jef Driesen wrote: > > > The preprocessor stuff is automated. I only have to maintain a symbols > > file with a few #ifdef's in it: > > > > mylib_abc > > #ifdef MYLIB_XYZ_SUPPORT > > mylib_xyz > > #endif > > But it's still two

Re: Questions on exporting functions from a shared library

2008-09-19 Thread Brian Dessent
Jef Driesen wrote: > The MSDN documentation [1] about this issue, gives me the impression > that applications have to relink when new symbols are added to the > library (when not using a DEF). And that's something I would like to > avoid. Actually this statement surprises me, so I'm probably just

Re: Questions on exporting functions from a shared library

2008-09-18 Thread Jef Driesen
Brian Dessent wrote: Jef Driesen wrote: What are the (dis)advantages of each method? I see differences in usage (see below), but are there technical differences as well? It sounds like you already are aware of all the tradeoffs. I don't think there's a technical difference in the end, i.e. t

Re: Questions on exporting functions from a shared library

2008-09-18 Thread Brian Dessent
Jef Driesen wrote: > What are the (dis)advantages of each method? I see differences in usage > (see below), but are there technical differences as well? It sounds like you already are aware of all the tradeoffs. I don't think there's a technical difference in the end, i.e. the results are the sa