Re: [openssl-users] Customize Windows library names
In messageon Fri, 16 Sep 2016 09:43:37 +0200, Kim Gräsman said: kim.grasman> Hi Richard, kim.grasman> kim.grasman> On Fri, Sep 16, 2016 at 12:08 AM, Richard Levitte wrote: kim.grasman> > In message on Thu, 15 Sep 2016 12:17:12 +0200, Kim Gräsman said: kim.grasman> > kim.grasman> > kim.grasman> I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed the kim.grasman> > kim.grasman> Windows build system now produces decorated lib names. kim.grasman> > kim.grasman> > For DLLs, yes. kim.grasman> > kim.grasman> > kim.grasman> The general pattern seems to be lib_[-].lib where kim.grasman> > kim.grasman> is only appended for 64-bit builds. kim.grasman> > kim.grasman> > Are you sure? Looking at my builds, I find libcrypto-1_1.dll and kim.grasman> > libssl-1_1.dll with the import libraries libcrypto.lib and kim.grasman> > libssl.lib. kim.grasman> kim.grasman> Ahem. I *was* sure, but with a clean build, I can see you're absolutely right. kim.grasman> kim.grasman> I must have mixed up the DLL names and import lib names at some point. kim.grasman> kim.grasman> Sorry about the confusion! That's for confirming. Cheers, Richard -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/ -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Customize Windows library names
Hi Richard, On Fri, Sep 16, 2016 at 12:08 AM, Richard Levittewrote: > In message > on Thu, > 15 Sep 2016 12:17:12 +0200, Kim Gräsman said: > > kim.grasman> I'm looking at integrating OpenSSL 1.1 in our tree, and I > noticed the > kim.grasman> Windows build system now produces decorated lib names. > > For DLLs, yes. > > kim.grasman> The general pattern seems to be lib_[-].lib > where > kim.grasman> is only appended for 64-bit builds. > > Are you sure? Looking at my builds, I find libcrypto-1_1.dll and > libssl-1_1.dll with the import libraries libcrypto.lib and > libssl.lib. Ahem. I *was* sure, but with a clean build, I can see you're absolutely right. I must have mixed up the DLL names and import lib names at some point. Sorry about the confusion! - Kim -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Customize Windows library names
On 9/15/2016 8:17 AM, Kim Gräsman wrote: Hi Thomas, On Thu, Sep 15, 2016 at 4:26 PM, Thomas J. Hruskawrote: The precompiled binary installer variants do this already. If you are using default builds, then that's possibly an option. We prefer to build from source to allow static and dynamic code analysis, for example. But do you have a link to these precompiled binary installers? Do you know how they accomplish plain names? Thanks, - Kim https://slproweb.com/products/Win32OpenSSL.html As to how: A batch file with a set of 'copy' commands ;) -- Thomas Hruska Shining Light Productions Home of BMP2AVI and Win32 OpenSSL. http://www.slproweb.com/ -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Customize Windows library names
In message <1446abd3-1599-24fe-1340-fc7f3da5e...@wisemo.com> on Fri, 16 Sep 2016 00:12:30 +0200, Jakob Bohmsaid: jb-openssl> On 16/09/2016 00:08, Richard Levitte wrote: jb-openssl> > In message jb-openssl> > jb-openssl> > on Thu, 15 Sep 2016 12:17:12 +0200, Kim Gräsman jb-openssl> > said: jb-openssl> > jb-openssl> > kim.grasman> I'm looking at integrating OpenSSL 1.1 in our tree, and I jb-openssl> > noticed the jb-openssl> > kim.grasman> Windows build system now produces decorated lib names. jb-openssl> > jb-openssl> > For DLLs, yes. jb-openssl> > jb-openssl> > kim.grasman> The general pattern seems to be jb-openssl> > lib_[-].lib where jb-openssl> > kim.grasman> is only appended for 64-bit builds. jb-openssl> > jb-openssl> > Are you sure? Looking at my builds, I find libcrypto-1_1.dll and jb-openssl> > libssl-1_1.dll with the import libraries libcrypto.lib and jb-openssl> > libssl.lib. jb-openssl> On 64 bit too? (see OP). Yup. The decoration is only supposed to happen on the DLL names. That's exactly what the following lines in the top build.info does: SHARED_NAME[libcrypto]=libcrypto-{- $config{shlib_major}."_".$config{shlib_minor} -}{- $target{multilib} -} SHARED_NAME[libssl]=libssl-{- $config{shlib_major}."_".$config{shlib_minor} -}{- $target{multilib} -} For the import libs, the static names (the 'index' of SHARED_NAME) are used. Cheers, Richard -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/ -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Customize Windows library names
On 16/09/2016 00:08, Richard Levitte wrote: In messageon Thu, 15 Sep 2016 12:17:12 +0200, Kim Gräsman said: kim.grasman> I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed the kim.grasman> Windows build system now produces decorated lib names. For DLLs, yes. kim.grasman> The general pattern seems to be lib_[-].lib where kim.grasman> is only appended for 64-bit builds. Are you sure? Looking at my builds, I find libcrypto-1_1.dll and libssl-1_1.dll with the import libraries libcrypto.lib and libssl.lib. On 64 bit too? (see OP). Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Customize Windows library names
In messageon Thu, 15 Sep 2016 12:17:12 +0200, Kim Gräsman said: kim.grasman> I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed the kim.grasman> Windows build system now produces decorated lib names. For DLLs, yes. kim.grasman> The general pattern seems to be lib_[-].lib where kim.grasman> is only appended for 64-bit builds. Are you sure? Looking at my builds, I find libcrypto-1_1.dll and libssl-1_1.dll with the import libraries libcrypto.lib and libssl.lib. Cheers, Richard -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/ -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Customize Windows library names
Hi Thomas, On Thu, Sep 15, 2016 at 4:26 PM, Thomas J. Hruskawrote: > > The precompiled binary installer variants do this already. If you are using > default builds, then that's possibly an option. We prefer to build from source to allow static and dynamic code analysis, for example. But do you have a link to these precompiled binary installers? Do you know how they accomplish plain names? Thanks, - Kim -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Customize Windows library names
On 9/15/2016 3:17 AM, Kim Gräsman wrote: Hi all, I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed the Windows build system now produces decorated lib names. The general pattern seems to be lib_[-].lib where is only appended for 64-bit builds. We'd prefer a naked lib name, at least for import libs (the DLL names are not important to us, as long as the import lib binds to the right name). Is there a supported way of dumbing down the names of libcrypto and libssl? I can resort to a private patch, but it'd be nice if Configure could be convinced to keep it simple out of the box. Thanks, - Kim The precompiled binary installer variants do this already. If you are using default builds, then that's possibly an option. -- Thomas Hruska Shining Light Productions Home of BMP2AVI and Win32 OpenSSL. http://www.slproweb.com/ -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] Customize Windows library names
Hi all, I'm looking at integrating OpenSSL 1.1 in our tree, and I noticed the Windows build system now produces decorated lib names. The general pattern seems to be lib_[-].lib where is only appended for 64-bit builds. We'd prefer a naked lib name, at least for import libs (the DLL names are not important to us, as long as the import lib binds to the right name). Is there a supported way of dumbing down the names of libcrypto and libssl? I can resort to a private patch, but it'd be nice if Configure could be convinced to keep it simple out of the box. Thanks, - Kim -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users