ncurses5-config --cflags and pkg-config --cflags have different beheaviour

[Misty De Meo]

Hi,

I've noticed an inconsistency between the include paths provided for
CFLAGS by ncurses5-config and the .pc file. ncurses5-config provides
both the include/ncursesw directory and the parent include directory,
while pkg-config only provides the include/ncursesw directory. Sample
output:

$ pkg-config --cflags ncursesw
-I/usr/local/Cellar/ncurses/5.9/include/ncursesw
$ ncursesw5-config --cflags
-I/usr/local/Cellar/ncurses/5.9/include/ncursesw
-I/usr/local/Cellar/ncurses/5.9/include

Since pkg-config is being installed to a location outside the default
header path, it's necessary for both to be specified in order for all
headers to be found. I've tested with both ncurses 5.9 and the latest
patches, and the behaviour is the same for both.

As a related issue, I've noticed that in the latest patches of
ncurses, pkg-config must be present in order for .pc files to be
installed - even if an explicit .pc install location is provided, and
it is not requested from pkg-config. (In 5.9, .pc files will be
installed if requested even if pkg-config is not installed.) I'm
curious if this is intentional, since it appears that pkg-config is
not used to actually generate the .pc files.

Best,
Misty De Meo