Обсуждение: What is the build strategy between make and meson?

Chao Li <li.evan.chao@gmail.com> writes:
> It is my first time trying meson build, and I got a bunch of warnings on my MacBook with macOS Sequoia 15.6.1:
> ...
> ../src/interfaces/libpq/fe-connect.c:5622:12: warning: 'ldap_init' is deprecated: first deprecated in macOS 10.10 -
useldap_initialize [-Wdeprecated-declarations] 

You would get those same warnings with configure/make too, if you
specified --with-ldap.  The relevant difference here is that configure
will not try to build with LDAP unless you tell it --with-ldap,
whereas meson's default behavior is to try to build with every option
that it can find supporting headers/libraries for.  That's a
philosophical difference between the build systems that we can't
really paper over.

> The other problem I encountered is that, when unicode map files are regenerated, “make” won’t auto rebuild
corresponding.o and lib files, but ninja does. That means “Makefile” has something to fix. But given ninja works,
should“Makefile” still be fixed? 

Probably.

> So, I want to clarify that:
> * Is it free for developers to choose make or meson?
> * If something works with one but the other, should that be fixed?

I believe the long-term plan is to abandon autoconf/make in favor of
meson, but the emphasis is on "long" --- any such decision is still
years away, I think.  In the meantime it's probably still worth
repairing deficiencies in the makefiles.  It's definitely worth
repairing deficiencies in the meson files, of which there are plenty.

            regards, tom lane

I wrote:
> Chao Li <li.evan.chao@gmail.com> writes:
>> The other problem I encountered is that, when unicode map files are regenerated, “make” won’t auto rebuild
corresponding.o and lib files, but ninja does. That means “Makefile” has something to fix. But given ninja works,
should“Makefile” still be fixed? 

> Probably.

BTW, did you use --enable-depend with configure?  If that fixes
the problem then there is no bug.  This is another philosophical
difference: autoconf lets you say whether to spend the overhead
to track build dependencies, meson/ninja does it always.  It might
be that --enable-depend isn't enough to capture this dependency,
in which case that's a bug worth fixing.

            regards, tom lane