Re: meson: Add _static and _shared suffixes to the library names
От | Jacob Champion |
---|---|
Тема | Re: meson: Add _static and _shared suffixes to the library names |
Дата | |
Msg-id | CAOYmi+n3S1bdqtCBm7abS9_mgeq5WgF6MhCsd_K5BQwAs=U43w@mail.gmail.com обсуждение исходный текст |
Ответ на | meson: Add _static and _shared suffixes to the library names (Nazir Bilal Yavuz <byavuz81@gmail.com>) |
Ответы |
Re: meson: Add _static and _shared suffixes to the library names
|
Список | pgsql-hackers |
On Tue, Aug 12, 2025 at 8:46 AM Nazir Bilal Yavuz <byavuz81@gmail.com> wrote: > The solution is changing the libraries' names [3]. Changing > conflicting libraries' names is actually enough but I wanted to add > _static and _shared suffixes to all of the libraries' names as I think > this is more future proof. > > Any feedback would be appreciated. Just as a kneejerk reaction, I think it'd be really strange if the Meson version of libpq-oauth.a was named libpq-oauth_static.a on disk, and clients had to figure out which build system was used in order to link. (Especially since the original name doesn't actually conflict with libpq-oauth-19.so.) > -libpq_so = shared_library('libpq', > +libpq_so = shared_library('libpq_shared', This, in particular, can't happen; it's akin to an SONAME bump. Is there a way to work around this problem in a way that affects Windows only? --Jacob
В списке pgsql-hackers по дате отправления: