Hi Patrice,
> As a side note, it would have been better to have a specific variable
> like LTLIBUNISTRING instead of using the global CPPFLAGS, but it is not
> a big deal either.
The absence of such a variable INCLIBUNISTRING is a trade-off between
convenience and complexity.
-L and -Wl options are collected in $LIBUNISTRING or $LTLIBUNISTRING
because typically only selected binaries of a package need to be linked
with libunistring; the other binaries should not see an increased startup
time or memory footprint.
The situation is different for -I options:
- It's harmless to have additional (possibly unused) -I options in $CPPFLAGS.
- It simplifies the Makefile to have all -I options in $CPPFLAGS.
- It also simplifies further configure tests if there's no need to
explicitly add $INCLIBUNISTRING to CPPFLAGS.
I first did it like this with libintl, ca. 25 years ago, and this approach
to modify CPPFLAGS works fine, except there were problems with config.cache
and early (old) versions of autoconf IIRC.
Bruno
