Re: Building libusb-win32 source for version 1.2.5

Xiaofan Chen <[email protected]>
Newsgroups gmane.comp.lib.libusb.devel.windows
Message-ID <CAGjSPUAcpHXJPsw=07ZAtPPBstCpdNvApH0dPS2W2v9WYhx13Q@mail.gmail.com>
On Mon, May 26, 2014 at 9:18 AM, Xiaofan Chen <[email protected]> wrote:
> On Sun, May 25, 2014 at 1:43 PM, Jason Micklewright <[email protected]> wrote:
>> Hi Xiaofan,
>> Thanks for the reply.
>> Firstly, I don't want to build it myself.  I have to document how it's done
>> for work purposes (long story).  I can't just refer to the libusb doc, I
>> have to actually get it building.
>
> Okay.
>
>> I did get the WDK 7.1.0 but can't get past the setenv.bat call that the make
>> calls somehow.  The make halts because setenv.bat is not called with any
>> parameters. How do parameter get passed into setenv.bat from the make call?
>> Is it something to do with running in a MinGW shell because I realize I'm
>> not doing that.
>> Thanks!
>
> No, the WDK build of libusb-win32 (almost) has nothing to do with
> MinGW, let alone MSys. Unless you want to build the MinGW
> import library, you do not need MinGW.
>
> In the ddk_make directory, edit make.cfg file to suit your
> build environment. Quite some of them are optional and
> are used to build the installer. You can safely comment
> out them.
>
> After that, run make.cmd under the command prompt (no
> need to under the WDK command prompt) to know the build
> options, choose the one you want.
>

Have you been able to sort out the issue? It seems there
is a problem with building with WDK 7.1.0 for the x86.

Here is what I get. x64 build is okay, x86 build failed. ia64
build is also okay.

Maybe Travis can help here.

C:\work\libusb-win32\libusb-win32-src-1.2.6.0\ddk_make>CMD /C make.cmd "arch=i64
" "winddk=C:\WinDDK\7600.16385.1\" clean
Libusb-Win32 directory = C:\work\libusb-win32\libusb-win32-src-1.2.6.0\
OACR is not supported for IA64
WinDDK ok. Target version = 0x502
Building (fre_wnet_IA64) make_dll.bat..
Building (fre_wnet_IA64) make_driver.bat..
Building (fre_wnet_IA64) make_test.bat..
Building (fre_wnet_IA64) make_test_win.bat..
Building (fre_wnet_IA64) make_install_filter.bat..
Building (fre_wnet_IA64) make_install_filter_win.bat..
[SafeCreateDir] .\i64

C:\work\libusb-win32\libusb-win32-src-1.2.6.0\ddk_make>CMD /C make.cmd "arch=x64
" "winddk=C:\WinDDK\7600.16385.1\" clean
Libusb-Win32 directory = C:\work\libusb-win32\libusb-win32-src-1.2.6.0\
OACR monitor running already
WinDDK ok. Target version = 0x502
Building (fre_wnet_AMD64) make_dll.bat..
Building (fre_wnet_AMD64) make_driver.bat..
Building (fre_wnet_AMD64) make_test.bat..
Building (fre_wnet_AMD64) make_test_win.bat..
Building (fre_wnet_AMD64) make_install_filter.bat..
Building (fre_wnet_AMD64) make_install_filter_win.bat..
[SafeCreateDir] .\x64

C:\work\libusb-win32\libusb-win32-src-1.2.6.0\ddk_make>CMD /C make.cmd "arch=x86
" "winddk=C:\WinDDK\7600.16385.1\" clean
Libusb-Win32 directory = C:\work\libusb-win32\libusb-win32-src-1.2.6.0\

Usage: "setenv <directory> [fre|chk] [64|x64] [WIN7|WLH|WXP|WNET] [bscmake] [no_
oacr] [separate_object_root]"

  By default, setenv.bat will set the environment variable NO_BROWSER_FILE.
  Using the "bscmake" option will cause setenv.bat to not define this variable.

  Example:  setenv d:\ddk chk        set checked environment
  Example:  setenv d:\ddk            set free environment for Windows
Win7 (default)
  Example:  setenv d:\ddk fre WIN7   set free environment for Windows
Win7 (default)
  Example:  setenv d:\ddk fre 64     sets IA-64 bit free environment
  Example:  setenv d:\ddk fre x64    sets x64 bit free environment
  Example:  setenv d:\ddk fre x32-64 sets x64 bit free environment
  Example:  setenv d:\ddk fre WXP    sets free build environment for Windows XP


Unable to configure WinDDK.


-- 
Xiaofan

------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.