Re: [openssl-users] build.info

We currently don't have per-engine support of the kind. The cleanest you can do is probably having a private config looking something like this: our %targets = ( 'mytarget' => { inherit_from=> [ 'whatever' ], dso_ldflags => '-lsomelib'

Re: [openssl-users] build.info

Thanks. That is correct. I'd like to specify -lsomellib for just one engine target in engines/build.info. On Tue, Sep 4, 2018 at 12:12 AM Jakob Bohm wrote: > On 04/09/2018 08:55, Wouter Verhelst wrote: > > On 9/3/18 9:05 PM, Thomás Inskip wrote: > >> Does anyone know how I can specify that a

Re: [openssl-users] build.info

On 04/09/2018 08:55, Wouter Verhelst wrote: On 9/3/18 9:05 PM, Thomás Inskip wrote: Does anyone know how I can specify that a specific shared library (in this case an engine) is dependent on a system-installed shared library (i.e. not built along with openssl)?.  Basically the equivalent of

Re: [openssl-users] build.info

On 9/3/18 9:05 PM, Thomás Inskip wrote: > Does anyone know how I can specify that a specific shared library (in > this case an engine) is dependent on a system-installed shared library > (i.e. not built along with openssl)?.  Basically the equivalent of > LDFLAGS += -lsomelib The GNU runtime

Re: [openssl-users] build.info

Using the linux env var LD_PRELOAD, maybe? ⁣Sent from BlueMail ​ On Sep 3, 2018, 15:05, at 15:05, "Thomás Inskip" wrote: >Does anyone know how I can specify that a specific shared library (in >this >case an engine) is dependent on a system-installed shared library (i.e. >not >built along with

[openssl-users] build.info

Does anyone know how I can specify that a specific shared library (in this case an engine) is dependent on a system-installed shared library (i.e. not built along with openssl)?. Basically the equivalent of LDFLAGS += -lsomelib -- openssl-users mailing list To unsubscribe:

[openssl-users] build.info documentation

Hello, Can anyone here point me in the direction to some documentation on build.info files? For the most part I’m creating mine using examples from other crypto ciphers but could use some more in depth explanation of what is going on when it is being parsed. More