Hi All,
I trying to build openssl 3.0.8 to generate x32/win32 libraries and header
files.
I used the following steps:
Opened the x86 Native Tools Command Prompt (Sets the environment to use
32-bit, x86-native tools to build 32-bit, x86-native code)
perl Configure --debug --openssldir="C:\OpenSSLW32\CommonFiles\SSL"
--prefix=C:\OpenSSLW32 VC-WIN32
nmake
However, I get the following error.
cmd /C ""cl" /Zs /showIncludes /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MDd
/W3 /wd4090 /nologo /Od -I"." -I"include" -I"apps\include" -D"L_ENDIAN"
-D"OPENSSL_PIC" -D"OPENSSLDIR=\"C:\\OpenSSLW32\\CommonFiles\\SSL\""
-D"ENGINESDIR=\"C:\\OpenSSLW32\\lib\\engines-3\""
-D"MODULESDIR=\"C:\\OpenSSLW32\\lib\\ossl-modules\""
-D"OPENSSL_BUILDING_OPENSSL" -D"OPENSSL_SYS_WIN32" -D"WIN32_LEAN_AND_MEAN"
-D"UNICODE" -D"_UNICODE" -D"_CRT_SECURE_NO_DEPRECATE"
-D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"DEBUG" -D"_DEBUG"
"apps\lib\tlssrp_depr.c" > apps\lib\libapps-lib-tlssrp_depr.d 2>&1"
"lib" /nologo /out:apps\libapps.lib
@C:\Users\user\AppData\Local\Temp\1\nmB79E.tmp
apps\lib\libapps-lib-fmt.obj : fatal error LNK1112: module machine type 'x64'
conflicts with target machine type 'x86'
NMAKE : fatal error U1077: '"lib" /nologo /out:apps\libapps.lib
@C:\Users\user\AppData\Local\Temp\1\nmB79E.tmp' : return code '0x458'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual
Studio\2022\Professional\VC\Tools\MSVC\14.38.33130\bin\HostX86\x86\nmake.exe" /
_build_sw' : return code '0x2'
Stop.
I also tried the x64_x86 Cross Tools Command Prompt - Sets the environment to
use 64-bit, x64-native tools to build 32-bit, x86-native code. That gave the
same error.
I would have expected that setup to be able to build the win32 version of the
objects and libraries.
What did I miss or is this not supported?
Thanks.
P.S. This all worked fine when I setup to build x64. Not errors and got libs
and objects for x64.
Thom Bentley | Senior Software Engineer | Medidata, a Dassault Systèmes
company<http://www.mdsol.com/>
This email and any attachments are intended solely for the use of the
individual or entity to whom it is addressed and may be confidential and/or
privileged.
If you are not one of the named recipients or have received this email in error,
(i) you should not read, disclose, or copy it,
(ii) please notify sender of your receipt by reply email and delete this email
and all attachments,
(iii) Dassault Systèmes does not accept or assume any liability or
responsibility for any use of or reliance on this email.
Please be informed that your personal data are processed according to our data
privacy policy as described on our website. Should you have any questions
related to personal data protection, please contact 3DS Data Protection Officer
https://www.3ds.com/privacy-policy/contact/
