Changes between Version 27 and Version 28 of libwdi/faq


Ignore:
Timestamp:
09/17/10 16:03:30 (3 years ago)
Author:
pbatard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • libwdi/faq

    v27 v28  
    1212  Absolutely. This can be very convenient if you have a multilib MinGW-w64 cross compiler installed on a Linux host for instance. You will of course need to have the WinUSB (DDK), libusb-win32 or your own user driver files available on the build platform.[[BR]]An example of configuring libwdi for cross-compilation using MinGW-w64, with the libusb-win32 driver, would go something like this:[[BR]]{{{  ./configure --host=x86_64-w64-mingw32 --with-libusb0="/usr/src/libusb-win32"}}}[[BR]] 
    1313 
    14 '''I am getting issues when running the embedder during cross-compilation''' 
     14'''The embedder fails to run during cross-compilation''' 
    1515  By default, the configure script expects your default build platform's compiler to be able to produce executables that run on said platform. This is necessary so that the build process can compile and run the custom embedder tool to add the driver files to the library. If however your default compiler can not produce executables that run on your build platform, this process will fail. This can occur for instance, if you are using a multilib MinGW-w64 on a Windows 32 platform, if the default for gcc is to produce 64 bit executables. If this is the case, you must define a {{{CC_FOR_BUILD}}} environment variable, with the relevant options to produce executables that work on your platform. For instance, in the scenario above, you would issue the following, to ensure that the embedder executable can run on 32 bit, before running configure:[[BR]]{{{  export CC_FOR_BUILD="x86_64-w64-mingw32-gcc -m32}}} 
    1616