Can I set the names of the DLLs/LIBs created during the build?

I want to have debug and optimized DLLs/LIBs for use by developers who need them to link their or open source code. I can manually rename the LIBs, but I can't rename the DLLs since the LIBs provide the original name of the DLLs. Any suggestions? I know that the DCMTK team built their own DLLs

RE: Building x32 libraries on x64 windows machine

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

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

Library and DLL names on Windows X64

Hi All, I had to change the names of the .lib files to: "dcmtkcrypto_d.lib" - debug version "dcmtkcrypto_o.lib" - release version (optimized) "dcmtkssl_d.lib"- debug version "dcmtkssl_o.lib"- release version (optimized) This was required by the DCMTK team's CMak

RE: Can we provide --debug and --release on a single build?

d as building with -O0), you're best bet, is to build with -g and -O3, then use objcopy to separate the debug sections into their own file, then strip the debug info from the initial dso. This is how most distributions create their debuginfo packages On Wed, Jul 10, 2024 at 1:22 PM BENTLEY Tho

RE: Can we provide --debug and --release on a single build?

st distributions create their debuginfo packages On Wed, Jul 10, 2024 at 1:22 PM BENTLEY Thom via openssl-users mailto:openssl-users@openssl.org>> wrote: Hi, I was wondering if the build scripts could handling providing –debug and –release for a build. Would this create release and debug lib

Can we provide --debug and --release on a single build?

Hi, I was wondering if the build scripts could handling providing -debug and -release for a build. Would this create release and debug libraries in a single build? Thanks. P.S. I know I could try it, but I thought others might want to know later too. Perhaps an update in the INSTALL.md file.

RE: Missing header file ts_local.h in install location.

.org>> > Sent: Friday, June 28, 2024 11:54 AM > To: BENTLEY Thom mailto:thom.bent...@3ds.com>>; Tomas > Mraz > mailto:to...@openssl.org>>; > openssl-users@openssl.org<mailto:openssl-users@openssl.org> > Subject: Re: Missing header file ts_local.h in install l

RE: Missing header file ts_local.h in install location.

m Bentley | Senior Software Engineer | Medidata, a Dassault Systèmes company<http://www.mdsol.com/> From: Matt Caswell Sent: Friday, June 28, 2024 11:54 AM To: BENTLEY Thom ; Tomas Mraz ; openssl-users@openssl.org Subject: Re: Missing header file ts_local.h in install location. On 28/06/2024 16

Re: Missing header file ts_local.h in install location.

Y Thom via openssl-users wrote: > Thanks. Yes, I saw that they became opaque. > The code I’m building works fine with 1. 1. 1w but we need to move to > 3. 0. 8 at least. > Here are the errors I see. > > On 28/06/2024 16:29, BENTLEY Thom via openssl-users wrote: > Thanks. Yes

RE: Missing header file ts_local.h in install location.

iiJ8sLVdiV6SYZo$>[github[.]com] Tomas Mraz, OpenSSL On Fri, 2024-06-28 at 14:09 +, BENTLEY Thom via openssl-users wrote: > > > > Hi All, > > I build and installed version 3.0.8 on Windows with Visual Studio > using the instructions provided. > I copied

RE: Missing header file ts_local.h in install location.

ley | Senior Software Engineer | Medidata, a Dassault Systèmes company<http://www.mdsol.com/> From: Matt Caswell Sent: Friday, June 28, 2024 10:18 AM To: BENTLEY Thom ; openssl-users@openssl.org Subject: Re: Missing header file ts_local.h in install location. On 28/06/2024 15: 09, BENTLEY

Missing header file ts_local.h in install location.

Hi All, I build and installed version 3.0.8 on Windows with Visual Studio using the instructions provided. I copied the bin, include, and lib directories to a location that would be found by the CMake for the DCMTK toolkit version 3.6.8. When I attempt to build the DCMTK toolkit, I see that the

Re: Issue with install after using `perl Configure` to set --prefix and --openssldir

Subject: Re: Issue with install after using `perl Configure` to set - > -prefix and --openssldir > > > > > > Hello, you have to use "-- > openssldir=C: \OpenSSLInstallDir\CommonFiles\SSL" Regards, Tomas > Mraz, OpenSSL On Thu, 2024-06-27 at 16: 50 +, BENTL

Re: Issue with install after using `perl Configure` to set --prefix and --openssldir

6-27 at 16: 50 +0000, BENTLEY Thom via openssl-users wrote: > > > > Hi All, > > I get an error running `perl Hello, you have to use "--openssldir=C:\OpenSSLInstallDir\CommonFiles\SSL" Regards, Tomas Mraz, OpenSSL On Thu, 2024-06-27 at 16:50 +, BENTLEY T

Issue with install after using `perl Configure` to set --prefix and --openssldir

Hi All, I get an error running `perl Configure --openssldir "C:\OpenSSLInstallDir\CommonFiles\SSL" --prefix=C:\OpenSSLInstallDir VC-WIN64A` target already defined - C:\OpenSSLInstallDir\Common Files\SSL (offending arg: VC-WIN64A) If I remove --openssldir "C:\OpenSSLInstallDir\CommonFiles\SSL",

RE: Issue building after configuring for VC-WIN64A (version 3.0.8)

e is a remaining object file somewhere that didn't get rebuilt for x64 when you ran your second configure. Start with a clean tree, run vcvarsall.bat x64 to set up your tool chain, then Configure for VC-WIN64A and nmake, it should work fine. On Wed, Jun 26, 2024 at 3:20 PM BENTLEY Thom via op

Issue building after configuring for VC-WIN64A (version 3.0.8)

Hi All, I followed the instructions for building OpenSSL 3.0.8 at https://github.com/openssl/openssl/blob/openssl-3.0.8/NOTES-WINDOWS.md#native-builds-using-visual-c The nmake step failed with the following error: cmd /C ""cl" /Zs /showIncludes /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3