diff options
author | Andy Polyakov <appro@openssl.org> | 2018-03-03 23:09:52 +0100 |
---|---|---|
committer | Andy Polyakov <appro@openssl.org> | 2018-03-09 15:04:50 +0100 |
commit | 5936e8884bc6f3b9ff9abf8ebbeb772809882f92 (patch) | |
tree | f27c027f97291a3f9e7417e0b9d7ee19b74e9ab3 /Configurations/50-win-onecore.conf | |
parent | 6a145a32f2cc6c19263a3c02281ced074da03c8e (diff) |
Configurations/50-win-onecore.conf: add Windows 10 OneCore targets.
This includes even ARM targets.
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5502)
Diffstat (limited to 'Configurations/50-win-onecore.conf')
-rw-r--r-- | Configurations/50-win-onecore.conf | 56 |
1 files changed, 56 insertions, 0 deletions
diff --git a/Configurations/50-win-onecore.conf b/Configurations/50-win-onecore.conf new file mode 100644 index 0000000000..1207621e67 --- /dev/null +++ b/Configurations/50-win-onecore.conf @@ -0,0 +1,56 @@ +# Windows OneCore targets. +# +# OneCore is new API stability "contract" that transends Desktop, IoT and +# Mobile[?] Windows editions. It's a set up "umbrella" libraries that +# export subset of Win32 API that are common to all Windows 10 devices. +# +# TODO: drop onecore_downlevel.lib. + +my %targets = ( + "VC-WIN32-ONECORE" => { + inherit_from => [ "VC-WIN32" ], + # /NODEFAULTLIB:kernel32.lib is needed, because MSVCRT.LIB has + # hidden reference to kernel32.lib, but we don't actually want + # it in "onecore" build. + lflags => add("/NODEFAULTLIB:kernel32.lib"), + ex_libs => "onecore.lib onecore_downlevel.lib", + }, + "VC-WIN64A-ONECORE" => { + inherit_from => [ "VC-WIN64A" ], + lflags => add("/NODEFAULTLIB:kernel32.lib"), + ex_libs => "onecore.lib onecore_downlevel.lib", + }, + + # Windows on ARM targets. ARM compilers are additional components in + # VS2017, i.e. they are not installed by default. And when installed, + # there are no "ARM Tool Command Prompt"s on Start menu, you have + # to locate vcvarsall.bat and act accordingly. VC-WIN32-ARM has + # received limited testing with evp_test.exe on Windows 10 IoT Core, + # but not VC-WIN64-ARM, no hardware... In other words they are not + # actually supported... + # + # Another thing to keep in mind [in cross-compilation scenario such + # as this one] is that target's file system has nothing to do with + # compilation system's one. This means that you're are likely to use + # --prefix and --openssldir with target-specific values. 'nmake install' + # step is effectively meaningless in cross-compilation case, though + # it might be useful to 'nmake install DESTDIR=S:\ome\where' where you + # can point Visual Studio to when compiling custom application code. + + "VC-WIN32-ARM" => { + inherit_from => [ "VC-noCE-common" ], + defines => add("_ARM_WINAPI_PARTITION_DESKTOP_SDK_AVAILABLE"), + bn_ops => "BN_LLONG RC4_CHAR EXPORT_VAR_AS_FN", + lflags => add("/NODEFAULTLIB:kernel32.lib"), + ex_libs => "onecore.lib onecore_downlevel.lib", + multilib => "-arm", + }, + "VC-WIN64-ARM" => { + inherit_from => [ "VC-noCE-common" ], + defines => add("_ARM_WINAPI_PARTITION_DESKTOP_SDK_AVAILABLE"), + bn_ops => "SIXTY_FOUR_BIT RC4_CHAR EXPORT_VAR_AS_FN", + lflags => add("/NODEFAULTLIB:kernel32.lib"), + ex_libs => "onecore.lib onecore_downlevel.lib", + multilib => "-arm64", + }, +); |