I am trying to add this manifest to my PyInstaller compiled EXE:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity name="TestApp" processorArchitecture="amd64" type="win32" version="1.0.0.0"/>
<dependency>
<dependentAssembly>
<assemblyIdentity language="*" name="Microsoft.Windows.Common-Controls" processorArchitecture="amd64" publicKeyToken="6595b64144ccf1df" type="win32" version="6.0.0.0"/>
</dependentAssembly>
</dependency>
<asmv3:application xmlns:asmv3="urn:schemas-microsoft-com:asm.v3">
<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">
<dpiAware>true</dpiAware>
</asmv3:windowsSettings>
</asmv3:application>
</assembly>
When I use PyInstaller's --manifest option it isn't added to the EXE or combined in the generated manifest file. I couldn't even find a line saying it was doing anything with the manifest during build. I then used MT.exe to embed the manifest with no errors. This manifest file is a modification of the one generated by PyInstaller. I had to remove the compatibility section because MT.exe said there was no compatibility option in the namespace compatibility... I added the part in to declare the app has dpiAware. After I do this I can see the manifest section added in with ResourceHacker but when I go to run the program it says that can't open self and does not run. When I embed the manifest using ResourceHacker the program will load but is still larger then the screen with DPI scaling turned on like it just ignored the manifest file. I am using python 3.5.1 and kivy 1.9.1.