Re: [Shallows-devel] The mysteries of WIN32 linking

[Jon H. <jon...@gm...>]

Hi

since the dllExport thing must be written in front of every function,
it pollutes the code rather much. So the question is do we really need
 to make dll files at all or can we just create a static library?
Personally I would prefer to avoid  the pollution more than having
dlls, what do you think?

On 9/16/05, Johan Seland <jo...@if...> wrote:
> Hi.
> =20
>  I have now discovered how we must rig shallows to actually generate a
> proper DLL out of it. With this setup scons creates both a shallows.dll a=
nd
> shallows.lib file.
> =20
>  See http://www.flounder.com/ultimateheaderfile.htm for a
> bit of background.
> =20
>  Basically, every class and function declaration needs the following
> prepended to its declaration when we are building shallows:
> =20
>  class __declspec( dllexport ) Texture { ... }=20
> =20
>  When we are using shallows, they need the following declaration:
> =20
>  class __declspec( dllimport ) Texture { ... }
> =20
>  The trick is of course some macro magic in config.h:
> =20
>  #ifdef COMPILING_SHALLOWS
>  #define DllExport __declspec( dllexport )
>  #else
>  #define DllExport __declspec( dllimport )
>  #endif
> =20
>  And then add DllExport in front of every class and function declaration.
> =20
>  class DllExport Texture { ... }
> =20
>  I have a working copy of shallows with this enabled, but since it is a
> rather large change, I would like to hear your opinions on this.
>  (On Linux we of course always make the DllExport macro to be whitespace.=
)
> =20
>  Is this okay for all of you?
> =20
> --=20
> Help a man with his math problems and you get him off your back for a day=
.
> Teach a man math, and you scare him off for the rest of your life.
>=20
> Regards Johan Seland
> PhD Student
> Center of Mathematics for Applications=20
> University of Oslo