mesonbuild / mesonbuild/wrapdb

Mismatched wrap and `project()` names

Open
#2,565 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Meson
Stars
118
Forks
298
Avg merge
2d 2h
Merged PRs (30d)
24

Description

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 |

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the wrapdb validation or generation entry point that reads wrap names and project() names; no file or test is named in the issue. Review how the listed ports are represented and whether existing checks cover naming consistency. Done means the intended consistency rule is agreed and enforced with coverage for representative mismatches.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.