<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 12/20/2011 08:43 AM, Pierre Stirnweiss wrote:
<blockquote
cite="mid:CAOjaSmjnn10eN2ifqGRpENi+NVaxZqdkoBs3prkikhzUQJFKAA@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
I'd like to point to this thread regarding kde on windows and
poppler (by the way is there a way in Googlemail to refer to a
thread without copy/paste it?):<br>
<br>
<span> From: <b>Pierre Stirnweiss</b> <span><<a
moz-do-not-send="true"
href="mailto:pstirnweiss@googlemail.com">pstirnweiss@googlemail.com</a>></span><br>
Date: Sun, Mar 20, 2011 at 9:26 AM<br>
To: Calligra Suite developers and users mailing list <<a
moz-do-not-send="true" href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a>><br>
<br>
</span><br>
Just something to keep in mind:<br>
on windows MSVC, libpoppler is a static library ("because poppler
does not have import/export thing for the core(private) api" dixit
pinotree). Libpoppler is not meant to be used directly. For the
karbon pdf filter this is however what we do. This means that:<br>
-either we disable the filter on windows MSVC<br>
-or we link the filter to every library libpoppler was linked to.
these should be exactly the same ones. that solution is not very
practical to implement.<br>
<br>
So if during the course of refactoring, this could be
avoided/fixed, all the better.<span> <br>
<br>
</span></blockquote>
<br>
Welllll...<br>
1. We are going to use poppler-Qt and that is made for being used
directly.<br>
2. I do not see a problem with statically included libpoppler in
every shared lib using it on Windows. I mean Windows is certainly
the wrong OS[1] if you try to not duplicate code in libraries/DDL's
(I don't mean that negative it can have advantages like keeping
backward-compatibility).<br>
3. I would suggest to either create a patch against libpoppler or to
write a thin API-compatible DLL around it that preserves binary
compatibility. In any case this is 100% out-of-scope of our work
especially since there is the Windows-alternate for Windows to just
duplicate the binary. I mean there are 1001 better ways to invest
time to get the Windows binaries down. One of them is removing
expensive KDE-dependencies (should be way easier when kde-frameworks
is in place).<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://www.joelonsoftware.com/articles/APIWar.html">http://www.joelonsoftware.com/articles/APIWar.html</a> - I love the
SimCity workaround cause I love SimCity :-)<br>
<br>
</body>
</html>