Re: two bugs while building back on mingw

[Nicola Pero]

> > Can I ask one question then - is 'BUILD_libgnustep_gui_DLL' and
> > 'libgnustep_gui_DLL' a general standard for building unix stuff on
> > Windows, or is it more or less a gnustep-only trick ?
> > 
> > Because if it's a gnustep-only trick, we could modify it in the following
> > way:
> > 
> > 
> > #if GNUSTEP_WITH_DLL
> > 
> > #if BUILD_libgnustep_gui_DLL
> > #  define APPKIT_EXPORT  __declspec(dllexport)
> > #  define APPKIT_DECLARE __declspec(dllexport)
> > #else
> > #  define APPKIT_EXPORT  extern __declspec(dllimport)
> > #  define APPKIT_DECLARE __declspec(dllimport)
> > #endif
> > 
> > #else # GNUSTEP_WITH[OUT]_DLL
> > 
> > #  define APPKIT_EXPORT extern
> > #  define APPKIT_DECLARE
> > 
> > #endif
> 
> Although this is a generally used trick, this should be the right way to 
> resolve it, as we cannot be sure if the libraries we are including use 
> it exactly the same way. So we should only try to control what we can 
> control and that is the compilation of our own libraries. And yes this 
> trick should do it.

Perhaps a problem might be with static libraries ... If a library is
static, you don't want the __declspec(dllimport) to happen.  Manually
filtering all libraries is horrible but you are sure that, if you are
linking against many libraries and some are shared some are static, you
only use __declspec(dllimport) on the shared ones.

Perhaps __declspec(dllimport) for a static lib is harmless ... is it ?

Is libobjc shared on Windows ?