On 1/31/2017 5:24 AM, Rod Widdowson wrote:

>> We need support for OpenSSL 1.1.0 libraries, and so I think the ability
>> to override the variables on the command line seems like a good idea.
> I believe so, but it comes at the cost of downstream support. Once you "document" something it has to work forever - that’s why I like these changes, I can move our build over to a supported mechanism.

Within reason. If OpenSSL 1.1 becomes pervasive one day maybe we should
make it the default and anyone using an older OpenSSL can specify their
libs. Some breakage is ok, but we try to avoid it as much as possible.

>> Changing the static library to roll up all the dependencies in one big
>> library I think is a bad idea.
> It makes me itch and I would build both dll and lib from the same objs; but I'm not a usermode library specialist = the DLLs I usually author are kernel-mode drivers. In this case I'd follow the reviewers as to what to do (and in doing so I must mention that I understand that I forgo my right to whine after the event).
>
> So, what's needed? Do we (Kees and I) need to deconstruct the patch? Shall I start from scratch and do what I need and work with Kees to make it do what it should?

We are discussing this now in 1201 [1] so subscribe to that. As Daniel
mentioned there are discussions here, github or sometimes both. Once I
take a look at his patch I will have more input.

[1]: https://github.com/curl/curl/issues/1201

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2017-02-01