On Fri, Oct 12, 2012 at 6:28 PM, Peter Stuge <[email protected]> wrote: > Andreas Fritiofson wrote: >> > you have to make sure to set PKG_CONFIG_PATH >> >> PKG_CONFIG_PATH only *adds* to the default search path > > It's *prepended* to the default search path, so when set correctly it > doesn't matter that pkg-config would still look through the default > search path since the appropriate package has already been found,
Except that with build system's libs still in the path, pkg-config will lie about the availability of libs to configure-scripts that could detect absence of a certain lib and fallback to another. > but > I do agree that PKG_CONFIG_LIBDIR is the best choice. _PATH requires > less typing though. :) I rarely do cross compiling with pkg-config but in the few times I did, using _PATH (as suggested in several places) has bitten me at least once, which caused me to google up the proper solution. I don't think I've ever tried it though. /Andreas ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
