Changes between Version 32 and Version 33 of libwdi

Timestamp:

09/01/10 14:23:07 (3 years ago)

Author:

pbatard

Comment:

--

libwdi

@@ -3 +3 @@
 == About ==
 
-The aim of this project is to create a library that facilitates the foolproof installation of any USB driver on Windows, primarily for, but not limited to, usage with libusb applications.
+The aim of this project is to providing application developers and driver makers, with a convenient way of extracting and installing USB drivers on end-users systems. Such drivers can then be used with, but not limited to, with libusb applications like [http://libusb.org/ libusb 1.0] or [http://sourceforge.net/apps/trac/libusb-win32/wiki libusb-win32].
 
 If you have a question that cannot be answered in these pages, please send an e-mail to [mailto://libusb-devel@lists.sourceforge.net?subject=libwdi libusb-devel@lists.sourceforge.net].[[BR]]
 '''Make sure you have '[libwdi]' in the e-mail subject''' so that your question is dealt with appropriately. Or you can also try to mail [mailto://pbatard@gmail.com?subject=libwdi the developers] directly.
 
-== Features ==
+== Main Features ==
 
-  * all required driver files are provided by the library - no need for additional downloads.
-  * automated inf generation, or can be used with your own inf & driver files (if you have a WHQL driver for instance).
-  * compatible with 32 and 64 bit Windows platforms, from Windows 2000 to Windows 7 (untested on Windows 2003) with the possibility to either:
-   * produce 2 separate libraries, for 32 or 64 bit, or,
-   * produce a single library that covers both 32 and 64 bit at the same time.
-  * can either be integrated in your application, so that:
-   * a single executable application is distributed without the need for an additional driver installer, or,
-   * a separate standalone installer application is used along with the application.
+  * Automated driverless device detection
+  * Automated inf creation, using the name reported by the USB device
+  * Automated driver files extraction, for both 32 and 64 bit platforms
+  * Automated driver installation, including UAC elevation where necessary
+  * A single library, embedding all the required files. Can be statically or dynamically linked to an application, so that driver installation can be taken care automatically of when required.
+  * Ability to produce a single library that runs and can install drivers on any platform from Windows 2000 to Windows 7
+  * Ability to produce a single library that runs and can install drivers on both 32 and 64 bit versions of Windows
+ 
+== Additional Features ==
+ * Allows the embedding and selection of WinUSB, libusb0.sys (from libusb-win32) or your own USB driver (eg. WHQL drivers)
+ * Full locale support. All API strings are UTF-8, and the generated inf is UTF-16
+ * Open Source, with a proprietary application friendly license (LGPL v2.1)
 
 == Status ==
 
-As of 2010.06.04, libwdi is in functional beta, including the installer applications (in examples).
-An official release is planned once we are satisfied that all the basic functionality has been added and is behaving as expected.
+'''v1.0.1''' was released on 2010.09.01.
 
-For the Zadig driver installer application binaries, please see the [http://libusb.org/wiki/windows_backend#DriverInstallation Driver Installation section] of the libusb Windows backend page.
+If you want to download the Zadig driver installer application, please visit the [http://libusb.org/wiki/windows_backend#DriverInstallation Driver Installation section] of the libusb Windows backend page.
 
 == Documentation ==
@@ -41 +44 @@
   * [http://www.cygwin.com/ cygwin] (32 bit only).
 
-The recommended development environment to compile the library/apps is Windows DDK as it allows the building of a 32+64 bit compatible library, and ensures that the required WinUSB DLL files are available. If you need Windows 2000 compatibility, MinGW is the preferred development environment.
+The recommended development environment to compile the library/apps is Windows DDK as it allows the building of a 32+64 bit compatible library, and ensures that the required WinUSB DLL files are available. If you need Windows 2000 compatibility, a multilib version of MinGW-w64 is the preferred development environment.
 
 == Source ==
 
-The current development tree is available from the [http://git.libusb.org/ libusb git server] in the [http://git.libusb.org/?p=libwdi.git;a=shortlog libwdi] repository.
+* [http://libusb-winusb-wip.googlecode.com/files/libwdi-1.0.1.tar.gz libwdi-1.0.1.tar.gz]
+
+* The current development tree is also available from the [http://git.libusb.org/ libusb git server] in the [http://git.libusb.org/?p=libwdi.git;a=shortlog libwdi] repository.
 
 For those not familiar with git, here are the git commands you can use retrieve and compile the Windows branch:
@@ -77 +82 @@
 == To Do ==
 
+  * cross-compilation & embedder improvements
   * downloading vs embedding of the driver files
 
 == In Progress ==
 
+== Done ==
+
   * GUI sample application (beta)
   * Documentation
-
-== Done ==
-
   * allow the editing of the device name
   * libusb0.sys driver support
@@ -96 +101 @@
 == Development's status log ==
 
-  Please consult the '''[http://git.libusb.org/?p=libusb-pbatard.git;a=shortlog;h=refs/heads/wdi git log]''' or the WDI section of the '''raw''' [wiki:windows_backend_activity_log Activity Log].
+Please consult the '''[http://git.libusb.org/?p=libusb-pbatard.git;a=shortlog;h=refs/heads/wdi git log]''' or the WDI section of the '''raw''' [wiki:windows_backend_activity_log Activity Log].
 
 == Development Links ==