mcpp/.gitignore at main · mcpp-community/mcpp · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
# mcpp's own build output (mcpp build / mcpp pack)
target/
# mbench's run cache: one fingerprinted directory per configuration
.mbench/
# Python bytecode from bench/tools/*.py
__pycache__/
*.py[cod]

# mcpp's per-workspace xlings sandbox + lockfile + diagnostic logs
/.xlings/
.sisyphus
.claude
mcpp.lock
doctor.log
/.mcpp-bmi/

# editor / OS
.DS_Store
*.swp
*.swo
.vscode/
.idea/

# generated module artifacts
*.gcm
*.pcm
*.ifc
*.ddi
compile_commands.json
.cache/

# xmake control-arm build (bench/: xmake.lua builds mcpp for the
# build-engine benchmark; these are its artifact + resolved-config dirs)
/build/
/.xmake/

# benchmark scratch. bench-work/ holds generated fixtures (regenerated on every
# run, and large); reports are per-host and belong in an artifact, not in git.
/bench-work/
/bench/bench-work/
bench-report.json
bench/bench-report.json
# --project mode writes the measured build's stdout/stderr next to the project
bench-child.log
.mcpp.toml.bench-backup

# ⚠️ An empty file a shell redirection left behind. It was committed in #436
# and lived on `main` for a week; the name reads like a variable that was meant
# to be expanded (`> $binDir`) and was not. Listed so the same slip is caught
# next time rather than reviewed again.
binDir
examples/*/target/

# `mcpp test` writes a per-invocation scratch dir here.
.mcpp/