n
>>> libssl.so or libcrypto.so if you are linked statically.
>>>
>>>
>>>
>>> -Tom
>>>
>>>
>>>
>>> *From:* openssl-users [mailto:openssl-users-boun...@openssl.org] *On
>>> Behalf Of *Aijaz Baig
>>> *Se
Sorry, but you are wrong : using libSSL.a in your libApp.so library does
not prevent you from using libSSL.so elsewhere in your program. In such
case, your program would still need libSSL.so
Le mer. 6 nov. 2019 à 09:38, Jakob Bohm via openssl-users <
openssl-users@openssl.org> a écrit :
> Regardi
Regarding #1: Using libSSL.a instead of libSSL.so should avoid using
libSSL.so by definition. Otherwise something went seriously wrong
with the linking. Same for any other library.
On 05/11/2019 18:22, Aijaz Baig wrote:
Thank you for the information.
I will address your points here:
1. I was
s-boun...@openssl.org] *On
>> Behalf Of *Aijaz Baig
>> *Sent:* Sunday, November 3, 2019 11:30 PM
>> *To:* openssl-users@openssl.org
>> *Subject:* static linking libssl and libcrypto
>>
>>
>>
>> I am trying to build a shared library that internally l
Baig
> *Sent:* Sunday, November 3, 2019 11:30 PM
> *To:* openssl-users@openssl.org
> *Subject:* static linking libssl and libcrypto
>
>
>
> I am trying to build a shared library that internally links openssl and
> crypto libraries statically so I can use it in a produ
Thank you for the information.
I will address your points here:
1. I was not aware of the fact that only those symbols that have been used
get imported when linking a library statically. So that very well could be
the case. I didn't get what you mentioned about the static linking
preventing the pr
: Sunday, November 3, 2019 11:30 PM
To: openssl-users@openssl.org
Subject: static linking libssl and libcrypto
I am trying to build a shared library that internally links openssl and crypto
libraries statically so I can use it in a production environment. To that end I
am using the following
Hello,
It's not an open-ssl issue, but more a compiler specific one.
With info you provided, I cannot tell you what you get as results, but two
points that may help:
1. regarding the 87 ssl symbols : when you link with a library, only the
useful symbols are imported. So, if the code in you
I am trying to build a shared library that internally links openssl and
crypto libraries statically so I can use it in a production environment. To
that end I am using the following Makefile
APPBASE=/home/AB/Documents/APP/APP_2.17.0
OPENSSL1.0.2p_INSTALL_LOC=/home/AB/Documents/APP/OpenSSL-1.0.2p-i
