yeah, then you need to build twice, once with each set of compiler flags. Renaming is a manual process IIRC
On Wed, Jul 10, 2024 at 1:43 PM BENTLEY Thom <thom.bent...@3ds.com> wrote: > Thanks Neil. > I just want to end up having a debug and release version of each library. > I need to rename them for use with DCMTK to the following. > > openssl: > > "dcmtkcrypto_d.lib" - debug version > > "dcmtkcrypto_o.lib" - release version (optimized) > > "dcmtkssl_d.lib" - debug version > > "dcmtkssl_o.lib" - release version (optimized) > > > > It seems they expect those file names and use them when generating a build > system with CMake. > > > > > > *Thom Bentley *| Senior Software Engineer | Medidata, a Dassault Systèmes > company <http://www.mdsol.com/> > > > > *From:* Neil Horman <nhor...@openssl.org> > *Sent:* Wednesday, July 10, 2024 1:32 PM > *To:* BENTLEY Thom <thom.bent...@3ds.com> > *Subject:* Re: Can we provide --debug and --release on a single build? > > > > you can supply both, but they don't create separate libraries. The --debug > and --release just set different optimization flags on the compiler (-g -O0 > vs -O3) If you want to be able to provide an optimized production build, > and supply a > > you can supply both, but they don't create separate libraries. The --debug > and --release just set different optimization flags on the compiler (-g -O0 > vs -O3) > > > > If you want to be able to provide an optimized production build, and > supply a level of debugability (though not as good 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 Thom via openssl-users < > 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 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. > > > > > > > > *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/ > <https://www.3ds.com/privacy-policy/contact/>* > > > > 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/ > > >
