Changes between Version 30 and Version 31 of windows_backend

Timestamp:

01/27/10 16:41:28 (3 years ago)

Author:

pbatard

Comment:

--

windows_backend

@@ -23 +23 @@
 Note that before you can install [http://code.google.com/p/tortoisegit/ TortoiseGit] you need to install [http://code.google.com/p/msysgit/ MSysGit] and make sure that, during the installation of MSysGit, when prompted to adjust the PATH environment, you select "Run Git from the Windows Command Prompt" (2nd option). Also, in the general settings of [http://code.google.com/p/tortoisegit/ TortoiseGit], the MSysGit path must point to the MSysGit bin directory (eg: C:Program Files (x86)Gitin")
 
-To compile this source, [http://sourceware.org/pthreads-win32/ pthread-win32] is also required, '''except for cygwin''', where pthread should be available by default.
+To compile this source, [http://sourceware.org/pthreads-win32/ pthread-win32] is also required, '''except for cygwin''', where pthread should be available by default.[[BR]]
+For convenience, precompiled versions of pthread-win32 for 32 bit and 64 bit Windows platforms are provided [http://libusb.org/attachment/wiki/windows_backend/pthread-win32_libusb.zip here].
 
 The following development environment are currently supported for libusb 1.0 on Windows:
   * [http://www.mingw.org MinGW] (32 bit version only, as the 64 bit version oh MinGW still has a bug that impacts libusb).
   * [http://msdn.microsoft.com/en-us/visualc/default.aspx Microsoft Visual C++ (Visual Studio)], either Express or full version, from version 6.0 (NB: currently missing project files for 6.0). You should be able to produce both win32 and x64 binaries with Visual C++, however x64 executables will require the use of a 64 bit version of [http://sourceware.org/pthreads-win32/ pthread-win32] compiled from their latest CVS source. See the [http://git.libusb.org/?p=libusb-pbatard.git;a=blob_plain;f=README_MSVC.txt README_MSVC.txt] for more details.
-  * [http://www.microsoft.com/downloads/details.aspx?FamilyID=2105564e-1a9a-4bf4-8d74-ec5b52da3d00 Windows DDK build environment], through the use of the 'sources' file in libusbos. Same caveats as above for x64.
+  * [http://www.microsoft.com/downloads/details.aspx?FamilyID=2105564e-1a9a-4bf4-8d74-ec5b52da3d00 Windows DDK build environment], through the use of the 'ddk_build.cmd' file. Same caveats as above for x64.
   * [http://www.cygwin.com/ cygwin].
 
-To create projects relying on libusb 1.0, please refer to how the executables are compiled in the examples/ directory.
+To create projects relying on libusb 1.0, please refer to how the executables are compiled for the various environments above.
 
 Finally, to access your USB devices with libusb-winusb, you need to download the [http://libusb-winusb-wip.googlecode.com/files/winusb%20driver.zip WinUSB driver files], customize the .inf for your device, and then install the driver.[[BR]]
-For more information on how to setup the WinUSB driver for your device, please see the [wiki:winusb_driver_installation WinUSB Driver Installation] page.
+For more information on how to setup the WinUSB driver for your device, please see the [wiki:winusb_driver_installation WinUSB Driver Installation] page or see the README file that comes with the driver.
 
 == Development Considerations ==
@@ -49 +50 @@
 == To Do ==
 
-  * HID
   * multithreading/concurrent access
   * automated WinUSB driver installation?
@@ -56 +56 @@
 == Done ==
 
+  * HID
   * device enumeration
   * descriptors retrieval