GitLab

Fix rawhide *.wxi & CI

See merge request !53

Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>

Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>

This reverts commit 826a5273.

Revert "data/wixl: fix wxi for rawhide"

See merge request !52

This partially reverts commit c6d776f8

.

All of the gstreamer removals were incorrect because the files in
question still exist. The missing DLLs broke virt-viewer spice audio
support.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Drop jasper from gdk-pixbuf

See merge request !51

This dep was removed in gdk-pixbuf release 2.42.0
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Support all CustomAction Execute types properly

See merge request !47

Add sys.BUILDARCH preprocessor variable.

See merge request !48

Strip scheduling condition nodes.

See merge request !49

Default Win64 to true on 64-bit arch

See merge request !46

Add IniFile support to Wixl.

See merge request !50

The <IniFile> tag allows creating INI files from an MSI installer. It
works by populating two MSI tables, IniFile and RemoveIniFile, with
the filename, section, key and values to add/remove, and scheduling two
new steps, WriteIniValues and RemoveIniValues, when those tables are not
empty.

The Windows Installer parser for conditions does not like leading or
trailing spaces. This means that fairly common constructs like

    <Custom Action='dostuff' After='InstallServices'>
        (NOT Installed) AND (NOT REMOVE)
    </Custom>

will have the "wrong" condition `    (NOT Installed) AND (NOT REMOVE)`,
leading to the windows installer framework raising an error when
executing the action.

To avoid this, we simply strip the leading and trailing spaces of
conditions.

This variable can be used to know which target we are currently building
against (as set by the --arch argument).

The same logic is used as for Component::Win64 auto-detection introduced
in the previous commit.

This commit does two things: It sets the correct flags for all types of
CustomAction Execute types (mostly figured through experimentation), and
only sets NO_IMPERSONATE flag if the resulting type has the IN_SCRIPT
type set (which is in-line with Microsoft's documentation of the
NO_IMPERSONATE flag: It's an in-script option).

This should allow SET_PROPERTY custom actions to work. Previously, they
would be set to SET_PROPERTY | NO_IMPERSONATE, which is an invalid
custom action type that Windows' msiexec would complain about.

In WiX Toolset, the Component::Win64 attribute takes the correct value
depending on the `--arch` flag being built for. The official
documentation for Win64 says this:

> The default value is based on the platform set by the -arch switch to
> candle.exe or the InstallerPlatform property in a .wixproj MSBuild project:
> For x86 and ARM, the default value is 'no'. For x64, ARM64, and IA64,
> the default value is 'yes'.

This commit reproduces this behavior: If Win64 is unset, it defaults to
true when building for x64 and IA64 (WixL doesn't support ARM64 yet).

Improve UpgradeVersion element handling

See merge request !45

Support DefaultVersion and CompanionFile in File element

See merge request !43

Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>

Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>