Re: [PATCH] Add an ldflags_sl meson build option - Mailing list pgsql-hackers

From Matt Smith (matts3)
Subject Re: [PATCH] Add an ldflags_sl meson build option
Date
Msg-id MW6PR11MB8310CBC483B9F27381E1C0F08C72A@MW6PR11MB8310.namprd11.prod.outlook.com
Whole thread Raw
In response to Re: [PATCH] Add an ldflags_sl meson build option  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: [PATCH] Add an ldflags_sl meson build option
List pgsql-hackers
An example of a shared library-specific flag is -shared on linux or -dynamiclib on darwin.



From: Peter Eisentraut <peter@eisentraut.org>
Sent: Tuesday, June 17, 2025 7:01 PM
To: Matt Smith (matts3) <matts3@cisco.com>; pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: [PATCH] Add an ldflags_sl meson build option
 
On 17.06.25 00:50, Matt Smith (matts3) wrote:
> I have a Bazel toolchain that sets different linker flags for exe/shared
> lib.
>
> I wanted to build postgresql shared libs with meson using the same
> toolchain flags that I build all my other 3rd party deps in Bazel.
>
> Currently for postgresql builds, we set LDFLAGS to the Bazel toolchain
> executable flags which means that any postgresql shared_library() gets
> the exe flags.

Ok, but what kinds of flags does that build system want to pass through,
what kinds of effects are you looking for?

pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin
Next
From: Fujii Masao
Date:
Subject: Re: pg_dump misses comments on NOT NULL constraints