Re: meson: Non-feature feature options
| От | Nazir Bilal Yavuz |
|---|---|
| Тема | Re: meson: Non-feature feature options |
| Дата | |
| Msg-id | CAN55FZ3GLXkWHpVwwU=OpLxid2vjSSsvrpW8MRPMWzC3JRvD5w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: meson: Non-feature feature options (Daniel Gustafsson <daniel@yesql.se>) |
| Ответы |
Re: meson: Non-feature feature options
Re: meson: Non-feature feature options |
| Список | pgsql-hackers |
Hi,
On Thu, 9 Mar 2023 at 16:54, Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 9 Mar 2023, at 14:45, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
>
> > How about we just hardcode "openssl" here instead? We could build that array dynamically, of course, but maybe we
leavethat until we actually have a need?
>
> At least for 16 keeping it hardcoded is an entirely safe bet so +1 for leaving
> additional complexity for when needed.
We already have the 'ssl_library' variable. Can't we use that instead
of hardcoding 'openssl'? e.g:
summary(
{
'ssl': ssl.found() ? [ssl, '(@0@)'.format(ssl_library)] : ssl,
},
section: 'External libraries',
list_sep: ', ',
)
And it will output:
ssl : YES 3.0.8, (openssl)
I don't think that using 'ssl_library' will increase the complexity.
Regards,
Nazir Bilal Yavuz
Microsoft
В списке pgsql-hackers по дате отправления: