On 11/09/2015 08:19 AM, Andreas Wehrmann wrote: > On 11/06/2015 02:33 PM, Christian Grothoff wrote: >> On 11/06/2015 02:25 PM, Olaf Buddenhagen wrote: >>> I don't mind refactoring -- though I obviously can't talk anything >>> specific here until I gain some grasp of the code. >>> >>> It's the dynamic loading idea that I really don't feel like >>> implementing... I'd leave that to anyone who has an actual use case for >>> it. >> Oh, that's almost trivial. Don't worry about that. The key is to have a >> header which precisely defines the API for the SSL backend(s). >> > > I followed this discussion and agree with Christian in that a > plugin-like interface > is most probably the "best" solution when it comes to supporting > different SSL backends. > > I just wanted to throw in that it might nice to have the ability to get > around without dynamic loading after all. > I don't know the current state of uCLinux, but I've had my hands on > systems, where dynamic loading doesn't work. > This would effectively break SSL for those users.
With GNU libtool, you get static linking on platforms that don't support dynamic linking (or by forcing it manually), so nothing would be lost.
0xE29FC3CC.asc
Description: application/pgp-keys
