> Working on this now. Curious what people think of this, and if there's a
> better way that I'm missing (other than ditching MS which unfortunately
> isn't an option at the moment).
Just offer your libraries only as DLLs... that bypasses this whole
mess. That is what many people who distribute
> > #if BUILDING_LIBFOO && HAVE_VISIBILITY
> > #define LIBFOO_DLL_EXPORTED
__attribute__((__visibility__("default")))
> > #elif BUILDING_LIBFOO && defined _MSC_VER
> > #define LIBFOO_DLL_EXPORTED __declspec(dllexport)
> > #elif defined _MSC_VER
> > #define LIBFOO_DLL_E
On July 25, 2009, Ralf Wildenhues wrote:
> * David Byron wrote on Tue, Jun 30, 2009 at 12:22:52AM
> CEST:
>
> > In the case where a build directory is configured for
> > static only (e.g. invoked with --disable-shared) I can
> > add -DLIBFOO_STATIC to one of the CPPFLAGS variables,
> > but if a b
Hello David,
* David Byron wrote on Tue, Jun 30, 2009 at 12:22:52AM CEST:
> Sorry if this is a FAQ. I'm building a library using the pr-msvc-support
> branch of libtool so I'm using native MSVC tools. When building a shared
> lib I'm doing one of the methods prescribed here:
>
> http://www.gnu.
