Message-ID: From: "apgrucza (@apgrucza)" To: "postgresql-interfaces/psqlodbc" Date: Mon, 06 May 2024 11:55:26 +0000 Subject: Re: [postgresql-interfaces/psqlodbc] PR #6: Use mimalloc to improve performance and reduce memory allocation lock contention In-Reply-To: References: List-Id: X-GitHub-Author-Login: apgrucza X-GitHub-Comment-Id: 2095838818 X-GitHub-Comment-Type: issue_comment X-GitHub-Edited-At: 2024-05-08T12:44:51Z X-GitHub-Issue: 6 X-GitHub-Repo: postgresql-interfaces/psqlodbc X-GitHub-Type: comment X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/pull/6#issuecomment-2095838818 Content-Type: text/plain; charset=utf-8 I just took a deeper look too. `installer.mak` is not even used by `buildInstallers.ps1`, so changing that file won't help. In `buildInstallers.ps1` there is [a call to Get-RelatedDlls](https://github.com/postgresql-interfaces/psqlodbc/blob/3869efe76653ce9e56edf10478e30dcf1072123c/installer/buildInstallers.ps1#L242) which uses `dumpbin.exe` to inspect `libpq.dll` and figure out its dependencies. As long as the `bin` directory referenced in `configuration.xml` contains these libraries, `dumpbin.exe` will find them and they will be included in the installer. That's why it worked when I changed `configuration.xml` to reference the EDB installation (`Get-RelatedDlls` returned `libssl-3-x64.dll libcrypto-3-x64.dll libintl-9.dll libwinpthread-1.dll libiconv-2.dll`). So, there should be no need to change the release code. As you say, we still need to figure out how to get the 32-bit versions of those libraries. @winpg was the one who always prepared and announced psqlODBC releases. Perhaps he could provide some insight here, or is he also unavailable?