[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gap-dev-discuss] ready packages, release candidates

From: Riccardo Mottola
Subject: Re: [Gap-dev-discuss] ready packages, release candidates
Date: Wed, 06 Jun 2012 09:53:07 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120429 Firefox/12.0 SeaMonkey/2.9.1

Hi Sebastian,

Sebastian Reitenbach wrote:

I don't know well how to handle this in a good way, I am not that expert
in make+configure.
Perhaps we could tweak the PDF inspector.

But I think That PDFKit is not linked well, one should not need to add
the linker path stuff.
For example, if you compile a gnustep applicaon, you do not need to add
al paths of libxml. libtiff, etc needed to compile base and gui.
For me, libxml, libtiff etc are installed in /usr/local/lib, the same place 
all other gnustep libraries get installed. Therefore, it will just find them. 
is in a different location. Where do you have libfreetype installed on Linux? 
On my
opensuse box, its in /usr/lib64 where I guess the make will just find it and 
pick it up
easily. I guess the configure script for the Inspectors need to be enhanced to 
with that. But for the ports tree, I'm fine with setting the environment 
This is easy enough for me ;) Since its done this way for years, I don't think
its a reason to hold back a GWorkspace release.

I added -Wl,-rpath of the freetype library as an LDFLAG for OpenBSD. TOgether with other fixes, I can compile now pdfkit and gworkspace without any additional options set at runtime on OpenBSD 5.0/x86

Let me know! The less hassle in the packages and the more standard it is, the better!

I only miss FreeBSD9/clang and I would release i could even release anyway with this version of xpdf.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]