[cairo] [PATCH] building libcairo-2.dll on Linux
behdad at behdad.org
Mon Apr 16 14:07:17 PDT 2007
On Mon, 2007-04-16 at 16:22 -0400, Hans Breuer wrote:
> On 16.04.2007 09:02, Tor Lillqvist wrote:
> > Behdad Esfahbod writes:
> > > BTW, don't we need
> > > to define cairo_public to __declspec(dllexport) and
> > > __declspec(dllimport) for win32? I don't see any code for that. Or is
> > > that not needed because of cairo.def?
> If there would be a cairo.def it could replace the __declspec(dllexport)
> with one major drawback: the .def file would need to be different depending
> on the configuration (e.g. with or without PNG, freetype, etc.).
> AFAIR this was the reason to not choose the .def file approach but go for
> the cairo_public define, but maybe I'm wrong. Read yourself in the
> following thread:
Yeah, I remember that the only reason we introduced cairo_public was
that too. And like you say, lacking autotools, the cairo.def approach
is not that effective.
Should we switch over? It's just a few lines.
> > Marking functions for export is unnecessary as cairo.def takes care of
> > listing them.
> I thought cairo.def was not part of the distribution but looking at
> Makefile.am shows me I was wrong. The approach there still misses
> reconfiguration without auto* tools.
> Also at least the condition for cairo-pdf.h exports seems wrong. IIRC it
> does work without Freetype since quite some time.
> -------- Hans "at" Breuer "dot" Org -----------
> Tell me what you need, and I'll tell you how to
> get along without it. -- Dilbert
> cairo mailing list
> cairo at cairographics.org
"Those who would give up Essential Liberty to purchase a little
Temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin, 1759
More information about the cairo