Re: Library and DLL names on Windows X64

[J Decker <d3ck0r@xxxxxxxxx>]

On Fri, Jul 12, 2024 at 9:03 AM BENTLEY Thom via openssl-users <openssl-users@xxxxxxxxxxx> wrote:

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)

 

what were the names previously?  And why was the change required? 

This was required by the DCMTK team’s CMake configuration steps.

Without doing this the configuration failed to find the correct parts of OpenSSL.

See: https://github.com/DCMTK/dcmtk/blob/59f75a8b50e50ae1bb1ff12098040c6327500740/INSTALL#L634

I noticed that their OpenSSL 1.1.1w zip file has DLLs with different names, too.
They are named:
dcmtkcrypto-1_1-x64.dll

dcmtkcrypto_d-1_1-x64.dll

dcmtkssl-1_1-x64.dll

dcmtkssl_d-1_1-x64.dll

 

Is there a option when building my own OpenSSL 3.0.8 libraries that will name the libraries and DLLs like this?

Is renaming them manually going to be OK?  Will the DLL be found when the application that requires it attempts to load it?
I’m just getting back into Windows development after many years.

Windows will only link to A DLL... the name of which comes from a .lib file at link time, unless you're using LoadLibraryEx() (equivalent of dlopen)  and loading possible options yourself.... so No, it will not be found.

renaming them manually is fine, as long as they are renamed before linking to other build products.

 

Thanks

 

 

Thom Bentley | Senior Software Engineer | Medidata, a Dassault Systèmes company

 

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/