On Fri, Apr 19, 2013 at 1:09 AM, Jan Schiefer <[email protected]> wrote:
> Windows requires an explicit declaration which entry points are to be
> made visible ("exported") from a shared library. I solved this with an
> external declaration (DEF file). Since I did this, I have also noted
> that some of the "public" functions in the codec2 library are decorated
> with CODEC2_WIN32SUPPORT macros, so that may be the preferable approach?
> This would work for everything other than c2sim, which needs access to
> some of the more private parts of the codec2 library. Not sure what to
> do about that one.
Linux can be made to behave like Windows. This performs better,
so it is the right thing to do. WxWidgits and glibc are done this way.
A short explanation: http://gcc.gnu.org/wiki/Visibility
Much more: http://www.akkadia.org/drepper/dsohowto.pdf
c2sim is probably best fixed by having it include the C files.
It's test code that needs to do abnormal things, so having it
do #include "../whatever/stuff.c" is fairly reasonable.
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
