Any one know where the .pc configuration files for pkg-config have gone in suse 9.0 ? they are not in /usr/lib/pkgconfig. Atleast not the gtk group. To get the .pc file, I have been rebuilding the source packages and copying the .pc file to the pkgconfig dir. any information would be appreatiated.
On Tue, 09 Dec 2003 23:13:53 -0800 Tech Department <tech@zip51.com> wrote:
Any one know where the .pc configuration files for pkg-config have gone in suse 9.0 ? they are not in /usr/lib/pkgconfig. Atleast not the gtk group. To get the .pc file, I have been rebuilding the source packages and copying the .pc file to the pkgconfig dir.
Well I found them but I don't know how to use them. /opt/gnome/lib/pkgconfig I was looking to didge's (one of the SUSE people) sylpheed-claws .spec and I found rm -rf $RPM_BUILD_ROOT%{prefix}/include/sylpheed rm $RPM_BUILD_ROOT%{prefix}/%{_lib}/pkgconfig/sylpheed-claws.pc So I was wondering why he deleted them. New sylpheed-claws use the .pc file to compile ghostscript-viewer plug-in. I've been able to produce a rpm but things are really messed. The generated sylpheed-claws.pc is not suited for SUSE. So I just added a hand written one in the source directory, changed the PKG_CONFIG_PATH on the fly and go on... but this is definitively an awfull solution. The best thing I can imagine would be to write a patch to change configure.ac and leave the source tar.bz2 file intact. Then actually install the sylpheed-claws.pc... Furthermore even include are deleted but they are used to compile the plug-ins... it would be more logical to build a sylpheed-devel too. Since I'm relatively new to building packages I was wondering what could be the way that has less eco-impact and can keep coherence and good relationships with original suse packages... clues? advices?
participants (2)
-
Ivan Sergio Borgonovo
-
Tech Department