Mismatched wrap and `project()` names

[bgilbert]

We have a number of ports where the wrap name doesn't match the first argument to project(). This doesn't seem to matter much (maybe it's slightly confusing) but it'd be easy enough to add a sanity check to enforce consistency in the future. Is that worth doing?

Wrap name	project() name
adamyaxley-obfuscate	obfuscate
arduinocore-avr	libarduinocore-avr
arrow-cpp	arrow
catch	Catch2
crow	Crow
docopt	docopt.cpp
fuse	libfuse
gee	libgee
google-benchmark	benchmark
grpc	gRPC
gumbo-parser	gumbo
imgui-docking	imgui
imguizmo	ImGuizmo
implot	ImGui Plotting Library
libexif	exif
libffmpegthumbnailer	ffmpegthumbnailer
libopenjp2	openjp2
libsigcplusplus-3	libsigc++
libtiff	tiff
libupnp	pupnp
libXinerama	libxinerama
libXrandr	libxrandr
libXrender	libxrender
libXv	libxv
libyaml	yaml-0.1
lua	lua-5.4
ludocode-mpack	mpack
mpark-patterns	MPark.Patterns
muellan-clipp	clipp
ogg	libogg
openblas	OpenBLAS
opencl-headers	OpenCLHeaders
orcus	liborcus
pcg	pcg-cpp
quazip	QuaZip
sdl2_image	sdl2-image
sdl2_mixer	sdl2 mixer
sergiusthebest-plog	plog
unittest-cpp	UnitTest++
vulkan-memory-allocator	VulkanMemoryAllocator
xxhash	xxHash
yajl	YetAnotherJSONParser

[neheb]

Doesn’t look like it.

[eli-schwartz]

To cite the meson documentation on project():

The project name can be any string you want, it's not used for anything except descriptive purposes. However since it is written to e.g. the dependency manifest is usually makes sense to have it be the same as the project tarball or pkg-config name. So for example you would probably want to use the name libfoobar instead of The Foobar Library.

I'm not certain how strong that argument really is. "The Foobar Library" is more human readable ("descriptive purposes") but "libfoobar" is more machine readable ("sbom manifests"). Different projects may care more about different sides of that. It's not like we have a pretty_name: kwarg today.

[stephanlachnit]

Another one is msgpackc-cxx, which is now called msgpack-cxx. Reminds me to update the project name next time I'll update it...