<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Module path in CMakeFileLists"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73057#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Module path in CMakeFileLists"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73057">bug 73057</a>
from <span class="vcard"><a class="email" href="mailto:krishnapg@yahoo.com" title="Gopalakrishna Palem <krishnapg@yahoo.com>"> <span class="fn">Gopalakrishna Palem</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=73057#c1">comment #1</a>)
<span class="quote">> why would you include poppler in a different build system?</span >
I see what you mean - but there are some cases where its easier to embed
poppler as sub-directory and issue cmake from the top level font-end app -
specially on Windows based machines, where poppler dependency binaries are not
easy to get (so all are built from source).
Also, in general, its usually a practice to "append"/"prepend" module paths
than overwrite them.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>