http://bugs.winehq.org/show_bug.cgi?id=11222
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #3 from Anastasius Focht focht@gmx.net 2008-01-24 10:37:19 --- Hello,
I don't see any problems embedding manifests into PE files. That tool ships with most Microsoft Platform SDKs or Visual Studio Installations (2005).
The "mt.exe" version I used for testing is: 5.2.3790.2075 (from VS.NET 2005). winever: wine-0.9.53-289-g71f81bf
Test run with simple manifest and small test PE:
--- snip --- wine mt.exe -nologo -manifest "test.manifest" -outputresource:test.exe fixme:advapi:RegisterEventSourceA ((null),".NET Runtime"): stub fixme:advapi:RegisterEventSourceW (L"",L".NET Runtime"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x00000000,0x33e66c,(nil)): stub err:eventlog:ReportEventW L"Error enumerating shim databases - 234" fixme:advapi:DeregisterEventSource (0xcafe4242) stub --- snip ---
The test PE file gets updated and has the manifest resource correctly embedded (I checked with PE tools).
So what's your problem?
1. State the exact version of tools you use. Make sure you use a recent version. 2. Manually execute the command line on wine console (not within build environment) - just to be sure it's really related to mt.exe itself.
E.g. "C:\Program Files\Microsoft Visual Studio 8\VC\bin\mt.exe" -manifest "blah.manifest" -outputresource:"blah.exe" ...
Regards