summaryrefslogtreecommitdiffstats
path: root/windows/pica-client.exe.manifest.in
blob: b30df694d972bbfcc8f169509ac695796b5f378b (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

  <assemblyIdentity
      type="win32"
      name="picapica.im.pica-pica.pica-client"
      version="@PICA_WINDOWS_VERSION@"
      processorArchitecture="*"
  />

  <description>Pica Pica Messenger</description>

  <!-- Use the themed version 6 common controls.  Without this dependency
       Windows loads the Windows 95 era comctl32.dll and Qt's native dialogs
       and widget style fall back to the unthemed look. -->
  <dependency>
    <dependentAssembly>
      <assemblyIdentity
          type="win32"
          name="Microsoft.Windows.Common-Controls"
          version="6.0.0.0"
          publicKeyToken="6595b64144ccf1df"
          language="*"
          processorArchitecture="*"
      />
    </dependentAssembly>
  </dependency>

  <!-- Run with the privileges of the invoking user.  This also stops the
       installer detection heuristics from asking for elevation just because
       the file name or the resources contain words like "setup" or "update",
       and it disables registry/file system virtualization. -->
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"/>
      </requestedPrivileges>
    </security>
  </trustInfo>

  <!-- Declare which Windows versions this program was tested against.  An
       unlisted program is reported the version of the newest OS it claims
       support for, and may silently get compatibility shims applied. -->
  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <application>
      <!-- Windows Vista -->
      <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
      <!-- Windows 7 -->
      <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
      <!-- Windows 8 -->
      <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
      <!-- Windows 8.1 -->
      <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
      <!-- Windows 10 and Windows 11 -->
      <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
    </application>
  </compatibility>

  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <!-- Allow paths longer than MAX_PATH in the file transfer code.  This
           has no effect unless the machine also has the LongPathsEnabled
           policy turned on, so it is safe on older systems. -->
      <longPathAware xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">true</longPathAware>

      <!-- Deliberately no dpiAware/dpiAwareness setting here: the Qt windows
           platform plugin selects the DPI awareness mode itself at startup,
           and a value in the manifest would override it.  Add one only
           together with the matching Qt high DPI attributes. -->
    </windowsSettings>
  </application>

</assembly>