> On 2 Dec 2024, at 22:12, Darek Ślusarczyk <dslusarc...@splunk.com> wrote:
> According to the postgresql-17 requirements > https://www.postgresql.org/docs/17/install-requirements.html > the minimum required version of openssl is 1.0.2. > In that version, the naming convention on windows is still ssleay32.[lib|dll] > and > libeay32.[lib|dll] instead of libssl.[lib|dll] and libcrypto.[lib|dll]. > It changed in version 1.1.0 > https://github.com/openssl/openssl/issues/10332#issuecomment-549027653 Correct, nice catch. > I also submitted a pull request on GitHub, which can be found here: > https://github.com/postgres/postgres/pull/188 Thanks for submitting it here once the PR was auto-closed, we don't use Github as I believe the bot stated. > - ssl_lib = cc.find_library('ssl', > + ssl_lib = cc.find_library(['ssl', 'ssleay32'], I'm not a meson expert by any means but I was suprised to see this, libname is defined as str and not list[str] in the meson documentaion so I didn't expect that to work. Is the list prioritized in order in case both libs exist on the system? On a non-Windows system I wouldn't want libssleay32 to be picked up over libssl if it happened to exist etc. -- Daniel Gustafsson
