Re: pkg-config support for libs
Should the /usr/X11R6 heirarchy be added to pkgconfig's default config? Perhaps it would be better if pkg-config provided an opaque way to add directories to the search paths. Does it have a config file in /etc. My Debian system doesn't have anything in /etc for pkg-config. It understands the PKG_CONFIG_PATH environment variable, but I'm not sure it has any config file. A polite request to the pkg-config people to add /usr/X11R6/lib/pkg-config (or whatever) to the default might not go astray, as if X were to begin using pkg-config it would be a common place to look. Craig Ringer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: pkg-config support for libs
On Wed, 2003-09-24 at 12:30, Craig Ringer wrote: Should the /usr/X11R6 heirarchy be added to pkgconfig's default config? Perhaps it would be better if pkg-config provided an opaque way to add directories to the search paths. Does it have a config file in /etc. My Debian system doesn't have anything in /etc for pkg-config. It understands the PKG_CONFIG_PATH environment variable, but I'm not sure it has any config file. A polite request to the pkg-config people to add /usr/X11R6/lib/pkg-config (or whatever) to the default might not go astray, as if X were to begin using pkg-config it would be a common place to look. See discussion the xdg-list archives over the last week or so https://listman.redhat.com/archives/xdg-list/ the approximate conclusion that has been arrived there is that some sort of $sysconfdir/pkg-config.conf file is the right approach, though someone still needs to implement that. Regards, Owen ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: pkg-config support for libs
Mike A. Harris wrote: Should the /usr/X11R6 heirarchy be added to pkgconfig's default config? Perhaps it would be better if pkg-config provided an opaque way to add directories to the search paths. Does it have a config file in /etc. My Debian system doesn't have anything in /etc for pkg-config. wt -- Warren Turkal President, GOLUM, Inc. http://www.golum.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: pkg-config support for libs
On Sun, 2003-09-21 at 22:38, David Dawes wrote: On Sun, Sep 21, 2003 at 09:06:43PM -0500, Warren Turkal wrote: David Dawes wrote: I think you have your perspective backwards. Autotools is supposed to handle system differences for the software package, not impose requirements on the underlying system. Autotools do not require pkg-config. It just makes autotools significantly easier to implement in a portable way for libs. X libraries are already installed on countless systems, and they're not going to magically acquire .pc files just because you say you need them. If an autotooled package requires them, the autotooled package is broken. Autotools do not require them...pkg-config just makes autoconf work a lot easier. I could write custom autoconf macros that test for Xrender in common locations, or we could put pkg-config support in and it would not have to guess. The .pc files tell it where to find the libs. I'd love to see your time machine. Dunno how else you're going to avoid writing those custom autoconf macros :-). Well, to some extent, I think the goal is that in 5 years people aren't *still* saying if you had a time machine, and could put those .pc files in 5 years ago... It's also possible to make macros that have fallback checks simpler and more reliable for systems that *do* have the .pc files, and to fall back to the old methods only where the .pc files don't exist. Finally, while autoconf includes macros for -lX11, there are lots of other libraries that XFree86 ships where there are no standard autoconf macros (libXv, libXxf86misc, and so forth.) .pc files for these would have considerable utility. One more thing to mention is that pkg-config is often useful when compiling on the command line or in one off make files. gcc -o mytest mytest.c `pkg-config --libs --cflags x11` Is, if not easier to type, easier to remember, than specifying the flags (-L/usr/X11R6/lib -lX11 -lm, usually, for XFree86, if it's installed in the standard location) manually. Regards, Owen ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: pkg-config support for libs
On Mon, 22 Sep 2003, Mike A. Harris wrote: We move the XFree86 supplied .pc files into /usr/lib/pkgconfig/ where the default pkgconfig configuration can find them. A better fix would be either making XFree86 install them into /usr/lib/pkg-config by default, or making the default configuration file for pkgconfig contain the X11 pkgconfig directory. Thoughts? (Under most normal circumstances) XFree86 tries not to install anything outside of /usr/X11R6/ I'm not clear whether it should be the job of the XFree86 installer, or whoever packages it for a distribution to put files into /usr/lib/pkgconfig ? -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: pkg-config support for libs
On Mon, Sep 22, 2003 at 10:03:58AM -0400, Owen Taylor wrote: On Sun, 2003-09-21 at 22:38, David Dawes wrote: On Sun, Sep 21, 2003 at 09:06:43PM -0500, Warren Turkal wrote: David Dawes wrote: I think you have your perspective backwards. Autotools is supposed to handle system differences for the software package, not impose requirements on the underlying system. Autotools do not require pkg-config. It just makes autotools significantly easier to implement in a portable way for libs. X libraries are already installed on countless systems, and they're not going to magically acquire .pc files just because you say you need them. If an autotooled package requires them, the autotooled package is broken. Autotools do not require them...pkg-config just makes autoconf work a lot easier. I could write custom autoconf macros that test for Xrender in common locations, or we could put pkg-config support in and it would not have to guess. The .pc files tell it where to find the libs. I'd love to see your time machine. Dunno how else you're going to avoid writing those custom autoconf macros :-). Well, to some extent, I think the goal is that in 5 years people aren't *still* saying if you had a time machine, and could put those .pc files in 5 years ago... It's also possible to make macros that have fallback checks simpler and more reliable for systems that *do* have the .pc files, and to fall back to the old methods only where the .pc files don't exist. Finally, while autoconf includes macros for -lX11, there are lots of other libraries that XFree86 ships where there are no standard autoconf macros (libXv, libXxf86misc, and so forth.) .pc files for these would have considerable utility. One more thing to mention is that pkg-config is often useful when compiling on the command line or in one off make files. gcc -o mytest mytest.c `pkg-config --libs --cflags x11` Is, if not easier to type, easier to remember, than specifying the flags (-L/usr/X11R6/lib -lX11 -lm, usually, for XFree86, if it's installed in the standard location) manually. In five minutes I can come up with a dumb script that extracts the same information from imake. Proof of concept attached. Works for Xv, Xxf86misc, etc. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes imake-config.sh Description: Bourne shell script
Re: pkg-config support for libs
David Dawes wrote: In five minutes I can come up with a dumb script that extracts the same information from imake. Proof of concept attached. Works for Xv, Xxf86misc, etc. Now dump the info into a .pc file so that it can be used with pkg-config. The point was not the method of my patch (I was following what is already in your cvs in xc/lib/Xft/). The point was to get pkg-config support. I will not deny that there was probably a better way to extract the info from imake. wt -- Warren Turkal President, GOLUM, Inc. http://www.golum.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: pkg-config support for libs
David Dawes wrote: I can only recall one case in my own experience where an autotooled program had a problem concerning X-related libs. Ironically those were exactly the libs that had pkgconfig support. The autotool and pkgconfig combination didn't know where to look for the needed .pc files. Assuming distribution packagers do their job, the .pc files will end up in the right place. For instance, I just committed the smaller version of the libX11 patch to Debian's XFree86 4.3 packages. By default, the pkg-config stuff is put into /usr/X11R6/lib/pkgconfig. For Debian (and possibly many others), the right directory is /usr/lib/pkgconfig. I manually shift the file (as many others are done). Warren -- President, GOLUM, Inc. http://www.golum.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
pkg-config support for libs
I see that there are some libs in the cvs with pkg-config support. Will patches be accepted that add this support for other libs as well? Warren -- President, GOLUM, Inc. http://www.golum.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: pkg-config support for libs
On Wed, Sep 17, 2003 at 06:17:15PM -0500, Warren Turkal wrote: I see that there are some libs in the cvs with pkg-config support. Will patches be accepted that add this support for other libs as well? That some libs have pkg-config support shouldn't be seen as indicative of anything in particular. All of them are distributed separately by their primary author, which isn't true of the other libs in the XFree86 source tree. It's likely that all of them will be moved to the xc/extras tree along with most other externally maintained components in the XFree86 source tree. Do you have other reasons for adding pkg-config support? For example, what would it buy us? David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
