xmake-workflow
Skill351 starsChanged 3 months agoApache-2.0View on GitHub
Build and test the libuipc project using XMake. Use when building with xmake, running xmake f / xmake build / xmake run commands, selecting release/releasedbg/debug modes, or running Catch2 tests produced by xmake.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/cpp-format.mdcCursor rule
- .cursor/rules/self-improvement.mdcCursor rule
- cmake-workflowSkill
- commit-conventionSkill
- commitSkill
- cursor-rulesSkill
- documentSkill
- fix-issueSkill
- fix-prSkill
- formatSkill
- github-prSkill
- gpu-optimizationSkill
- project-structureSkill
- push-tagSkill
- repository-setupSkill
- review-prSkill
- run-testsSkill
- simulation-devSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run all xmake commands from the repository root (libuipc/).
- Very specific: line 16
Add -m releasedbg (RelWithDebInfo equivalent) or -m debug to change mode.
- Very specific: line 24
Keep -j low (e.g. -j8). NVCC is memory-hungry and can OOM with a high job count.
- Very specific: line 30
Test targets use the shared uipc_test rule in apps/tests/xmake.lua, which rewrites the binary basename to uipc_test_<target>.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
XMake Workflow for libuipc
Run all xmake commands from the repository root (libuipc/).
Configure
xmake f -cAdd -m releasedbg (RelWithDebInfo equivalent) or -m debug to change mode. Default is release.
Build
xmake build -j8Keep -j low (e.g. -j8). NVCC is memory-hungry and can OOM with a high job count.
Build one target: xmake build -j8 core.
Target Names vs. Binary Names
Test targets use the shared uipc_test rule in apps/tests/xmake.lua, which rewrites the binary basename to uipc_test_<target>. Use the target name for xmake build / xmake run; use the binary name only when executing the file directly.
| Target name | Binary name |
core, geometry, common, sim_case, regression, sanity_check, backend_cuda | uipc_test_<target> |
hello_affine_body, hello_simplicial_complex, wrecking_ball, pyuipc | same as target |
List every runnable target with xmake run --help.
Testing
Tests use Catch2. Run via xmake (recommended):
xmake run sim_case
xmake run backend_cudaOr execute the binary directly: ./build/<plat>/<arch>/<mode>/uipc_test_core (e.g. ./build/linux/x86_64/releasedbg/uipc_test_core; on Windows the path ends in .exe).
Catch2 flags passthrough:
--list-tests— list all test cases[tag]— filter by tag"test name"— run a specific test
Quick Reference
| Step | Command |
| Configure | xmake f -c (add -m releasedbg for RelWithDebInfo) |
| Build | xmake build -j8 |
| Build one target | xmake build -j8 <target> |
| List run targets | xmake run --help |
| Run test | xmake run <target> |
| Clean | xmake clean (add -a for all configs) |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.