WebAssembly / WebAssembly/wabt
[Question] CMake-generated targets vs top-level makefile
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.1k
- Forks
- 827
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 18
Description
Sorry if this has been answered elsewhere. I am building directly with CMake and curious about targets in provided Makefile vs the ones generated by CMake, in particular test-everything (Makefile) vs check (CMake) and update-gperf (Makefile only).
Readme doesn't seem to recommend using check, though it does work and seems at first glance to match what CI does. Not 100% sure if test-everything covers the same actions.
For update-gpref, it is probably possible to detect gperf and generate the command from CMake, and maybe even run it when source changes. Not sure if all platforms have gperf.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the repository Makefile targets test-everything and update-gperf with the CMake-generated check target, and inspect the README guidance for these commands. Document whether the targets cover equivalent actions and clarify how gperf generation is handled across supported platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100