[openssl-users] Customize Windows library names

[Richard Levitte]

In message <1446abd3-1599-24fe-1340-fc7f3da5e6c1 at wisemo.com> on Fri, 16 Sep 2016 00:12:30 +0200, Jakob Bohm <jb-openssl at wisemo.com> said:

jb-openssl> On 16/09/2016 00:08, Richard Levitte wrote:
jb-openssl> > In message
jb-openssl> > <CANt7B+feUe2W7627Nrw5bVOnZ1Wb5uQ4z57=ry9LwE7d0b28_w at mail.gmail.com>
jb-openssl> > on Thu, 15 Sep 2016 12:17:12 +0200, Kim Gräsman
jb-openssl> > <kim.grasman at gmail.com> 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<name>_<ver>[-<arch>].lib where
jb-openssl> > kim.grasman> <arch> 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         levitte at openssl.org
OpenSSL Project         http://www.openssl.org/~levitte/