Message-ID: From: "chrullrich (@chrullrich)" To: "postgresql-interfaces/psqlodbc" Date: Sun, 06 Oct 2024 14:46:56 +0000 Subject: Re: [postgresql-interfaces/psqlodbc] PR #64: MSI improvements In-Reply-To: References: List-Id: X-GitHub-Author-Login: chrullrich X-GitHub-Comment-Id: 2395466394 X-GitHub-Comment-Type: issue_comment X-GitHub-Edited-At: 2024-10-06T15:23:43Z X-GitHub-Issue: 64 X-GitHub-Repo: postgresql-interfaces/psqlodbc X-GitHub-Type: comment X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/pull/64#issuecomment-2395466394 Content-Type: text/plain; charset=utf-8 My exploration of both the PostgreSQL and psqlODBC build systems has not been overly successful (and it certainly did not help that PostgreSQL switched to Meson on Windows). I am able to build PostgreSQL in the most basic way, with essentially no optional features at all. The [censored] [censored] buildInstallers.ps1 ... [censored]. I managed to at least get it to pick up OpenSSL and could see it in libpq's dependencies, but the OpenSSL libraries did not show up in the PostgreSQL installation directory. psqlODBC installers include only those dependencies of libpq that are found in the same directory as libpq.dll, so I ended up with a package that installed a libpq with unresolved dependencies. I have no idea if I'm supposed to copy libssl-3.dll and libcrypto-3.dll manually; instead, I disabled the OpenSSL support again. Any advice on how this is meant to work will be greatly appreciated.