Changes between Version 10 and Version 11 of libwdi/reuse

Timestamp:

08/26/10 13:46:10 (3 years ago)

Author:

pbatard

Comment:

--

libwdi/reuse

@@ -17 +17 @@
   The trick is to use MinGW as the compiler along with the "-DWINVER=0x500" flag.
   ||=File(s): =||[http://git.libusb.org/?p=libwdi.git;a=blob;f=configure.ac /configure.ac] ||
-== Creating a Windows GUI application that use the latest Windows visual enhancements (Aero Glass look on Vista/Windows 7 for instance), even if compiled from MinGW/cygwin ==
+== Creating a Windows GUI application that use the latest Windows visual enhancements (Aero Glass look on Vista or Windows 7), even if compiled from MinGW/cygwin ==
   The default from all compilers, including Microsoft ones, is NOT to use the default look and feel from each platform, but to force the XP/2k one.[[BR]]
   To enable a more up to date look and feel in standard GUI applications, you need to manually embed the [http://git.libusb.org/?p=libwdi.git;a=blob;f=examples/common_controls.manifest common-controls manifest], as well as include <commctrl.h> in your source.
@@ -45 +45 @@
   ||=File(s): =||[http://git.libusb.org/?p=libwdi.git;a=blob;f=examples/common_controls.manifest common-controls manifest], [http://git.libusb.org/?p=libwdi.git;a=blob;f=examples/zadig_sources example DDK sources (Zadig)], [http://git.libusb.org/?p=libwdi.git;a=blob;f=examples/zadig.rc example MinGW manifest from .rc (Zadig)] ||
 == Creating Windows application from MSVC, WDK/DDK, MinGW and cygwin that require UAC elevation, even if compiled from MinGW/cygwin ==
+  The solution to that is similar to the above one, in that you need to use [http://git.libusb.org/?p=libwdi.git;a=blob;f=examples/elevation.manifest a manifest for elevation].[[BR]]
+  In our project, you will see that we combine multiple manifests were needed (this is the case for the Zadig example above for instance), as DDK is not able to merge separate manifests files. Also, recent versions of Visual Studio don't require an explicit manifest file for elevation, as this can be taken care of in Linker -> Manifest File -> UAC Execution Level.
+
+ ||=File(s): =||[http://git.libusb.org/?p=libwdi.git;a=blob;f=examples/elevation.manifest /examples/elevation.manifest]||
 == Running a 32 or 64 bit version of an embedded application depending on the platform ==
 == Compiling an project for both 32 and 64 bit ==