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.02 20:50 "[Tiff] vb port soon available", by Antoine
2005.06.02 21:00 "Re: [Tiff] vb port soon available", by Edward Lam
2005.06.03 06:04 "Re: [Tiff] vb port soon available", by Andrey Kiselev
2005.06.03 08:18 "Re: [Tiff] vb port soon available", by Antoine
2005.06.03 06:10 "Re: [Tiff] vb port soon available", by Andrey Kiselev
[...]

2005.06.02 21:00 "Re: [Tiff] vb port soon available", by Edward Lam

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?

-Edward

I finally realised what was going on and decided to get into the c of libtiff. I have basically put __stdcall in front of a bunch of functions so that they can be called from libtiff. I managed to get all the functions used in tiffcp done, so that should give some initial utility. The damn thing compiles! I will be writing a wrapper tomorrow or the next day. I am going to put it on sourceforge. It will be called libtiff4vb. I don't imagine there is any interest in putting it anywhere near the proper libtiff distro, but I thought some of you might like to know. If there is interest, and I write some good code, it can go anywhere.

I have just copied the licence from libtiff - is that going to be OK? (with sam and silicon graphics included)