Re: Building x32 libraries on x64 windows machine

2024-07-19 Thread Neil Horman
This error: fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86' says that you're set up for using x64 native tools, despite indicating you have opened the x86 native tool command Try running vcvarsall.bat x32 Which should force your environment to build in 32

RE: Building x32 libraries on x64 windows machine

2024-07-19 Thread BENTLEY Thom via openssl-users
Sorry. Friday afternoon brain. Forgot to do a `nmake clean` Thom Bentley | Senior Software Engineer | Medidata, a Dassault Systèmes company From: BENTLEY Thom Sent: Friday, July 19, 2024 3:48 PM To: openssl-users@openssl.org Subject: Building x32 libraries on x64 windo

Building x32 libraries on x64 windows machine

2024-07-19 Thread BENTLEY Thom via openssl-users
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:\OpenS

Re: Own HW Supported RSA provider

2024-07-19 Thread tomasz bartczak
Hi Levitte,Thanks for your answer.  Just follow up question.If I use the crypto library I can provide desired properties like in EVP_ASYM_CIPHER_fetch function. However when I use the ssl library, how to make sure it calls the mentioned EVP_ASYM_CIPHER_fetch function with properties required by