>> >> The current stumbling block for the cairo drivers is that they use >> pkg-config to get the correct paths and libraries to link in. This won't >> work on a cross-compiled environment unless you provide suitable >> pkg-config >> files from a cross-compiled version of cairo. This should be possible >> though. > > Yes. This may already be covered in the CMake cross-build wiki, but > instead > of setting PKG_CONFIG_PATH (which always sets the native pkg-config > default > path in addition to the non-native one you set), you should set > PKG_CONFIG_LIBDIR (which sets only the non-native path that you > specify and > which excludes the native pkg-config path).
I have read that in places to, and have yet fully understand the distinction between the two. We use PKG_CONFIG_PATH for cross builds all the time and get results. For one thing, how would pkg-config 'know' what is native and non-native? I wouldn't want a cross build to ever link to a native lib anyway. In a build system that needed both/many separate pkg-config environments would need to be specified as such anyway. In the case of plplot this is done with the separate steps for the native and cross build. In some things I've put together, more than one can be explicitly specified for different purposes in one step. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
