On Mon, May 12, 2025 at 8:49 AM Jacob Champion
wrote:
>
> On Mon, May 12, 2025 at 3:50 AM Christoph Berg wrote:
> > Since nothing in libpq should need curl for compiling, should we drop
> > it there instead?
>
> The static build (libpq.a) still needs libcurl. The module is only
> compiled for use
On Mon, May 12, 2025 at 3:50 AM Christoph Berg wrote:
> Since nothing in libpq should need curl for compiling, should we drop
> it there instead?
The static build (libpq.a) still needs libcurl. The module is only
compiled for use by the shared library.
--Jacob
Re: Jacob Champion
> Wolfgang reported over in [1] that I've missed a comma when appending
> to the PKG_CONFIG_REQUIRES_PRIVATE list, making libpq.pc look ugly:
>
> Requires.private: libssl, libcrypto libcurl
Is adding libcurl there even the right move? This will make all
programs using pkgco
