On Sat, Oct 13, 2012 at 2:04 AM, Peter Stuge <pe...@stuge.se> wrote:
> Here's an example for urjtag, which uses the pkg-config macros:
>
> ( export WD=/tmp/x-urjtag;
> export CROSS=i686-mingw32;
> export PKG_CONFIG_LIBDIR="${WD}"/lib/pkgconfig;
> mkdir -p "${WD}"/source && \
> cd "${WD}"/source && \
> git clone git://git.libusb.org/libusb.git && \
> git clone git://urjtag.git.sourceforge.net/gitroot/urjtag/urjtag && \
> cd libusb && \
> ./autogen.sh --prefix="${WD}" --host=$CROSS --disable-debug-log && \
> make install && \
> cd ../urjtag/urjtag && \
> ./autogen.sh --prefix="${WD}" --host=$CROSS --disable-python \
> --without-readline --with-libusb=1.0 --without-libftdi && \
> make install && \
> ls -l "${WD}"/*
> )
It's not as easy as you seem to think.
This will not generate a proper build. Binaries will expect to be
installed at /tmp/x-urjtag, which is not likely to be the case on the
host system, so will fail to find configuration files, for example.
For windows builds and OpenOCD specifically it's not a problem,
because we don't care about the autotools paths but instead hardcode
config file paths relative to the binary. Windows binaries in general
are not expected to depend on their install location, because Windows
is such a mess that it wouldn't work.
You may be able to get the desired result by playing around with
sysroot setting of configure and/or pkg-config, but that probably
brings on another set of complexities.
/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
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
