From: | "Matt Smith (matts3)" <matts3(at)cisco(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Add an ldflags_sl meson build option |
Date: | 2025-06-18 01:11:44 |
Message-ID: | MW6PR11MB8310CBC483B9F27381E1C0F08C72A@MW6PR11MB8310.namprd11.prod.outlook.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
An example of a shared library-specific flag is -shared on linux or -dynamiclib on darwin.
________________________________
From: Peter Eisentraut <peter(at)eisentraut(dot)org>
Sent: Tuesday, June 17, 2025 7:01 PM
To: Matt Smith (matts3) <matts3(at)cisco(dot)com>; pgsql-hackers(at)postgresql(dot)org <pgsql-hackers(at)postgresql(dot)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?
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2025-06-18 02:12:48 | Re: relrewrite not documented at the top of heap_create_with_catalog() |
Previous Message | Melanie Plageman | 2025-06-18 01:04:57 | Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin |