What is the build strategy between make and meson?

It is my first time trying meson build, and I got a bunch of warnings on my MacBook with macOS Sequoia 15.6.1:

```
chaol(at)ChaodeMacBook-Air build % ninja
[231/1835] Compiling C object src/interfaces/libpq/libpq.5.dylib.p/fe-connect.c.o
../src/interfaces/libpq/fe-connect.c:5622:12: warning: 'ldap_init' is deprecated: first deprecated in macOS 10.10 - use ldap_initialize [-Wdeprecated-declarations]
5622 | if ((ld = ldap_init(hostname, port)) == NULL)
| ^
/Library/Developer/CommandLineTools/SDKs/MacOSX15.5.sdk/usr/include/ldap.h:1526:1: note: 'ldap_init' has been explicitly marked deprecated here
1526 | ldap_init LDAP_P(( /* deprecated, use ldap_create or ldap_initialize */
| ^

<too long, so omitting the rest>
```

Should those warnings be fixed?

But “make” won’t generate those warnings.

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?

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?

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/