RE: [Plib-devel] Releasing PLIB 1.2 *soon*.

[Dave M. <Dav...@dy...>]

Steve Baker Wrote:
> I wanted to mention that I'd like to release PLIB 1.2 (a stable
> release) sometime soon.  I have a couple of mods of my own to
> put in - if anyone else needs to commit anything or knows of
> any significant problems that need fixing - please let me know
> so that we can arrange to catch all of these prior to release.
> 

Sam Stickland Wrote:
>The DLL changes simply require a:
>
>#ifdef WIN32
>    #define PU_EXPORT __dllspec(dllexport)
>#else
>    #define PU_EXPORT
>#endif
>
>in a common header file, and then PU_EXPORT has to be added to every
>function and variable prototype/declaration (after the return type, but
>before the prototype).  And, of course, some matches project files to
>generate the DLLs (I can supply VC++ version 6) (although it's probably
best
>to supply all new project files VC++ being what it is).
>
>I can supply a patch for the DLL and .so stuff - I'm not sure if it's worth
>it for the interface resizing stuff.
>

I would really like to see the patch for DLL stuff make it into PLIB 1.2
Can I go ahead and add that?  I'll use PLIB_EXPORT instead of PU_EXPORT and
apply the change to all of PLIB.  Each header file would have the following:


/* Some compilers use a special export keyword */
#ifndef PLIB_EXPORT
# ifdef __BEOS__
#  if defined(__GNUC__)
#   define PLIB_EXPORT     __declspec(dllexport)
#  else
#   define PLIB_EXPORT     __declspec(export)
#  endif
# else
# ifdef WIN32
#  define PLIB_EXPORT      __declspec(dllexport)
# else
#  define PLIB_EXPORT
# endif
# endif
#endif


This is the only way i know of that a non-opensource app
can use PLIB under BeOS or WIN32 without creating a branch
which would be a headache to maintain.

--Dave McClurg