AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2005.05.27 21:08 "[Tiff] creating a vb wrapper for libtiff", by Antoine
[...]
2005.06.03 08:18 "Re: [Tiff] vb port soon available", by Antoine
2005.06.03 17:10 "Re: [Tiff] vb port soon available", by Antoine
2005.06.03 17:36 "Re: [Tiff] vb port soon available", by Edward Lam
[...]

2005.06.03 17:10 "Re: [Tiff] vb port soon available", by Antoine

I think that a better approach would have been to add something like TIFF_EXPORT in front of all the functions that we need to export. And then we can just have some options to control this #define in config.h.

On Windows for example, one can use this to do away with the need for a .def file by doing:

#define TIFF_EXPORT __declspec(dllexport)

This would allow everything to go into one baseline. I detect multiple baselines because what happens if a bug gets fixed in only 1 of them?

How would people feel about putting a (stolen ungraciously from freeimage):

#define DLL_CALLCONV __stdcall

(with some decision thing to make it optional)

...

TIFF_EXPORTS

...

#ifdef FREEIMAGE_EXPORTS
#define DLL_API __declspec(dllexport)
#else
#define DLL_API __declspec(dllimport)
#endif // FREEIMAGE_EXPORTS
#endif // FREEIMAGE_LIB || !WIN32

In tiffio.h and then

DLL_API return_type DLL_CALLCONV TIFF_Function_Name(params);

for all of the functions exported? Does that sound like a plan? I am going to work on a script to do it in any case, seeing as I need it. I will post the script when I have it done.

Cheers
Antoine

--

G System, The Evolving GUniverse - http://www.g-system.at