On Fri, Oct 12, 2012 at 9:52 AM, Jonathan Dumaresq <[email protected]> wrote: > Peter Stuge wrote: >> and you have to make sure to set PKG_CONFIG_PATH > > This is where I dont' find many information. On my system this ENV var is > not set to anything. > > This var should be set to what ? /tmp/cross-compile/output ? >
I agree with you here. This is the difficult part and I do not see a good solution to use pkg-config under Linux for cross compile at least under the Linux distro I use: Ubuntu. Maybe the one Peter uses (Gentoo) and probably Fedora has some nice framework for MinGW cross. It is the same situation to do the native build under MinGW. pkg-config is kind of useless there. The way I solve the issue is to put the header file and lib file to the respective location (eg: MinGW include and lib directory. And this works very well for OpenOCD since it only needs a few external library (eg: libusb-win32, libftdi and libusb-1.0/libusbx). BTW, you may not want to use libusb-1.0.9 for Windows since it is very buggy. You can use libusb.git if you want to use it. But it is much easier if you use libusbx (libusb fork) Windows binary distribution. Actually that is what Freddie uses for his OpenOCD Windows binary build. http://libusbx.org/ http://sourceforge.net/projects/libusbx/files/releases/1.0.14/Windows/ -- Xiaofan ------------------------------------------------------------------------------ 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
