[cairo] Win32 Testsuite + .def file

[Owen Taylor]

On Thu, 2005-12-15 at 16:37 -0800, Vladimir Vukicevic wrote:

> > vlad: Was that change intentional? It seems like this changes what the
> > .def file that cairo tarballs ship contains. Don't know if that'd be a
> > bad thing.
> 
> Sorry, I thought I put in a ChangeLog entry.  It was intentional,
> though I didn't realize the .def file was in the tarball and not
> generated each time.  The problem is that without the -include, only
> the symbols for the surfaces with the -D there are exported.  So, for
> example, glitz isn't part of that list, and if you build without
> freetype bad things happen, etc.  I'm not sure what the .def file
> solution is; maybe we just ship a .def.win32 with a default set, but I
> have no idea what should be in that default set (I guess that .def
> file would be used for building with msvc?  Even then, you might not
> want to build, e.g. freetype/ps/pdf, and the like...).

I don't really see why a .def file is necessary at all ... when I 
built for Win32 last week, I just added something like:

#ifdef BUILDING_CAIRO
#define cairo_public __declspec(dllexport)
#else
#define cairo_public __declspec(dllimport)
#endif

To cairo-features.h. Then defined (in the visual studio project
settings) BUILDING_CAIRO. That removes all the worries about whether
the .def file matches the particular configuration.

Regards,
					Owen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/cairo/attachments/20051215/227d0d29/attachment.pgp