Build without Win32.mak, and using Universal C Runtime (UCRT)
windows: Check for APPVER, not VCVER for UCRT
When deciding whether UCRT is used (and thus no CRT merge modules), check for
Windows 10 rather than the version of Visual Studio, as we may be building with
an older SDK.
Build without Win32.mak, and using Universal C Runtime (UCRT)
windows: Check for APPVER, not VCVER for UCRT
When deciding whether UCRT is used (and thus no CRT merge modules), check for
Windows 10 rather than the version of Visual Studio, as we may be building with
an older SDK.
This is just a hack to get Appveyor builds to complete successfully.
Eventually we should get packages and installers to build correctly, and
even for x86 and x86_64 combined. But it's early days and this is
useful enough.
In order for the 64-bit FULL installer to install both the 64-bit
and 32-bit versions of gssapi.dll a merge module needs to be created
so that both versions can exist within the same install package.
Change-Id: Iaa979556e1691d3906e497f87e7d12cd89b1d980
When installing the gssapi.dll within the Heimdal\bin directory
make sure to install the version that has the assembly manifest.
Otherwise, the DLL cannot find the heimdal.dll.
Change-Id: Idd6f8f00db718f8a764e1cfa9d06d188ab22a313
gssapi.dll is supposed to be implementation agnostic. No version
numbers and no manifest required to load it. In addition to the
version that is installed as part of the assembly also include a
version that can be discovered by LoadLibrary() via PATH search.
Change-Id: I1865dd2ecec208745a40e699837bd2a888341a31
Create a heimdal-version.mak include file which can be included
in third party installer makefiles to determine which compiler and run
time library type was used to build the merge modules. It is the
responsibility of third party installer packages to include the Visual
Studio CRT merge modules that are required for execution.
Change-Id: Icec2f47755ef7cc5f7dde2e0426603dece7e4933
This reverts commit a759e5091f.
The policy assembly is now skipped on XP from within the policy assembly
itself so it can be safely installed elsewhere.
A bug in Fusion on XP causes downlevel issues with upgrade. The long
term fix is to duplicate the Fusion behavior. For now we just suppress
the install on XP
On XP there is a bug which prevents two installers from including a
policy assembly of the same name. Policy Assembly names are
<Product>.<Major>.<Minor>
For now do not install the policy assembly until we have a work around
for XP or a method of conditionally not installing the policy on XP.
Change-Id: If92bea3c625e6124eb64c2bcc3e5008a58f04404
When building a multiplatform installer 64-bit Heimdal.Command.msm
should not include the 32-bit components.
Change-Id: I5a3545d50edb69e982ea6b2febb45637764a8ca2
Remove third party plugins from installers now that they must be part
of the assemblies.
Add support for thirdparty heimdal-assemblies.wxs and heimdal-policy.wxs
files.
Change-Id: Idb29ebcf39b14ebcd2b01dc8c53b9bb7fbb8eaab
Note that the explanation of how to set CODESIGN_PKT is located
in windows/README.
Remove dead code.
Add an @arch@ substitution rule which is replaced by either "32" or "64"
depending upon $(CPU).
Change-Id: Ia009209aa7837109669172dcd841db846dcc9127
Windows file resources can be marked as Private, Special, Debug
and Pre-release. Extend the Heimdal Assembly name to include
designations for these various build options to ensure that
private, special, debug and pre-release builds do not conflict
with the assembly name reserved for public releases. This permits
a private, special, debug and pre-release build to be installed
side-by-side with the final release without interference.
Change-Id: I569ce2ff911ddbaebd81ba2e8b477ba6fb520502
The multiplatform installer must include the 32-bit command
merge module. When Heimdal.Command was split out into a separate
merge module it was left out.
Change-Id: I07b06d6dfff66e61869f1d8c81bb0f1bce281501
Heimdal plugins are not safe on windows. Plugins are bound to a
specific assembly and if the plugin assembly is not the same as
the Heimdal DLL that is loading the plugin heap corruption will
occur.
Change-Id: Icf43a989684c4aacd3c4a225482a9bed9b60e29d
Patchset 1ad02ec31a removed the
createAndRemoveOnUninistall actions from a number of registry keys.
Get the same behavior with the ForceDeleteOnUninstall Wix 3.x Attribute.
Change-Id: I8c0623fa39055844d10035cbffb3870cc2d39ec6
Breakout the version data from windows/NTMakefile.config
and move it to windows/NTMakefile.version. This new file
contains only version data. This permits version data to
be safely referenced by third party components.
In addition, add version range information for those versions
of Heimdal for which this release is a compatible upgrade. If
there is a forward incompatible change to the assembly ABI, it
is not a compatible upgrade. This version data is used to specify
the Windows assembly redirect range.
Change-Id: Ic9f156212599cc4277e2be812f29a6497801046c
kswitch.exe and klist.exe are kcc.exe installed and copied
under the alternate names. The installer script was missing
the required DestinationProperty to specify where the
destination files were to be placed.
Change-Id: Ia1e826a038459b1631f8452f8d7ef6f7ca02abac
