Re: [vdr] [PATCH] Install headers, add pkgconfig file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Mar 2008, Matthias Schwarzott wrote:
On Dienstag, 11. März 2008, clemens kirchgatterer wrote:
On Tue, Mar 11, 2008 at 12:27 AM, Matthias Schwarzott [EMAIL PROTECTED]
wrote:
On Montag, 10. März 2008, Ville Skyttä wrote:
So you can install .pc file anywhere you want if you add this location
to PKG_CONFIG_PATH.
So /usr/bin/pkg-config will always look into /usr/lib/pkgconfig.
We can either use
A. $(DESTDIR)/usr/lib/pkgconfig
or
B. $(DESTDIR)$(PREFIX)/lib/pkgconfig
For most installations A should be fine.
definitly B, otherwise it will not work for parallel installs of
different vdr versions in different $PREFIXes.
Ack!
BUT: B with default values from Makefile gives
/usr/local/lib/pkgconfig that by default is not in pkgconfig search-path.
And I wrote: For most installations ...
What would you think is the default?
case 1:
download pkg-config, extract it, run configure, make, make install
and you end up with pkg-config installed in /usr/local/bin and the default
search path will be /usr/local/lib/pkgconfig:/usr/local/share/pkgconfig
as the configure script sets:
pc_path='${libdir}/pkgconfig:${datadir}/pkgconfig'
if there is no '--with-pc_path=/my/path' given to configure.
case 2:
install an openSuSE-10.3 (i386) system with the prepackaged pkg-config RPM
and you end up with pkg-config installed in /usr/bin and the default search
path is /usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:
/usr/lib/pkgconfig:/usr/share/pkgconfig:/opt/kde3/lib/pkgconfig
case 3:
install a Debian-4.0 (x86_64) system with the prepackaged pkg-config DEB
and you end up with pkg-config installed in /usr/bin and the default
search path is /usr/local/lib/pkgconfig:
/usr/local/lib/pkgconfig/x86_64-linux-gnu:/usr/local/share/pkgconfig:
/usr/lib/pkgconfig:/usr/lib/pkgconfig/x86_64-linux-gnu:/usr/share/pkgconfig
case 4:
install FreeBSD and install the prebuilt pkg-config package or built it by
hand out of the ports tree and you end up with pkg-config installed in
/usr/local/bin and the default search path is /usr/local/libdata/pkgconfig:
/usr/local/lib/pkgconfig
Out of this four cases (there are probably more, one for every Linux
distribution on this planet), tell me which is the most reasonable
default?
Joerg
- --
The beginning is the most important part of the work.
-Plato
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFH1ps+SPOsGF+KA+MRAvWCAJ9Q8xP2Zywci6CxH+Y0dLhahaLo/ACeJsrR
xSPJC+0zZ/vWNoRm879qMTs=
=auza
-END PGP SIGNATURE-___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] portability or VDR on FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 7 Mar 2008, Joerg Pulz wrote: Replying to myself. The next patches are ready, this time for the mp3/mplayer plugins and the dvd plugin. The patches can be found at ftp://ftp.frm2.tum.de/pub/jpulz/VDR/ . I've written a small README.FreeBSD as quickstart guide available at the above link too. I've not attached the patches to this mail to not pollute the list with stuff of lower interest for the bigger part of the VDR community. And again, replying to myself. The next round of patches is there. Available at the same place as mentioned above. The README got an update too. There is still full Linux compatibility, so the patched version of VDR and the plugins can be compiled on a Linux box without any difference to the unpatched version. As always, comments are welcome. FYI, Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH1t5ISPOsGF+KA+MRAgYUAKDMAdZJe75PMFp1iztlkD1ldl9f5QCfQEKt G+3Tz55z0J/9pyjfuWPcEto= =M+bc -END PGP SIGNATURE- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Use pkg-config to find freetype/fontconfig flags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 8 Mar 2008, Clemens Kirchgatterer wrote: Ville Skyttä [EMAIL PROTECTED] wrote: FWIW, I think providing a pkgconfig file is very much a root solution (ditto $foo-config scripts, but *.pc are much simpler to write and read and have a unified interface). Lots of library packages (and also some others) provide them nowadays which is great, and has made the things you express dissatisfaction with in the above as well as other similar ones pretty much moot. i can't agree more. In fact, I think VDR should also provide a *.pc file. I ship one in Fedora's VDR packages, and a good deal of it would be applicable to upstream VDR too. Just let me know if you're interested and I'll have a look at making a upstreamable version of it. i would even say VDR is broken in the way it handles plaugins. VDR's Makefile should install all exported vdr headers in $(PREFIX)/include/vdr and provide a vdr.pc file (as you suggest). then plugins could be buildable outside of VDR's source directory and install themself in $(PREFIX)/lib/vdr. as any other plugin capable program out there i know. just my 2 cents ... clemens Clemens, you are so damn right! +1 from my side Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH0nFxSPOsGF+KA+MRArb3AKCG5dH73MNsSs53yspji2hV/v8zDwCgte11 CpaEgzbmHUsy7THwZgUQpa4= =lClI -END PGP SIGNATURE-___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Use pkg-config to find freetype/fontconfig flags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Content-ID: [EMAIL PROTECTED] On Thu, 6 Mar 2008, Klaus Schmidinger wrote: On 03/06/08 20:37, Ville Skyttä wrote: Hello, The attached patch makes VDR's Makefile use pkgconfig for finding libs and include dirs of freetype and fontconfig instead of making assumptions. How about putting that stuff at the same place everywhere? Why must it have to be somewhere else on every system? Klaus, how about accepting the case, that the world has more than one Linux distribution and in addition, there is not only Linux where VDR can run on. How about beeing a little bit less ignorant when it comes to VDR and portability. What do you think why we have tools like pkg-config or autotools and so many projects make use of it? Because its funny? I don't think so! What's the big deal with Villa's proposal to change two lines in the Makefile when it breaks nothing for you and makes life easier for other users? Sorry for beeing harsh Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH0TJeSPOsGF+KA+MRAsD1AKCdERUgFHIW444SvpkRvpwDrjsBcACdHCxz i82ezhk2fithcwziBJysTno= =jdQQ -END PGP SIGNATURE-___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] portability or VDR on FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Replying to myself. The next patches are ready, this time for the mp3/mplayer plugins and the dvd plugin. The patches can be found at ftp://ftp.frm2.tum.de/pub/jpulz/VDR/ . I've written a small README.FreeBSD as quickstart guide available at the above link too. I've not attached the patches to this mail to not pollute the list with stuff of lower interest for the bigger part of the VDR community. FYI, Joerg - -- The beginning is the most important part of the work. -Plato -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH0ZLJSPOsGF+KA+MRAkBuAKDL+IlOqmNV3Ovvhta8ZIOYnem4UwCeMpkw pUelj8VUSSJuw7rutnvFnos= =3dLl -END PGP SIGNATURE- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
