# Generated build tree: LLVM IR, objects, compiled apps, the headless render
# (build/out.ppm) and the docs site all land under build/ (see `bin/ludic-dev build` /
# `bin/ludic clean`). Root-anchored so a source dir named "build" elsewhere is never
# accidentally ignored. Nothing is written to the repo root any more.
/build/

# Archives are never tracked: the Kenney art is committed *extracted* under
# assets/kenney/**/ (PNG/tmx/License), while the original download .zips and any
# packaged plugin .zip are local-only build inputs/outputs.
*.zip

# the toolchain binaries (ludicc, ludic, ludic-dev, ludic-fmt, ludic-lsp) — all built
# into bin/ by the one-line bootstrap + `bin/ludic-dev build`; never checked in. The
# only thing published is the source and the LLVM-IR seed (selfhost/ludicc.seed.ll).
/bin/

# package manager (issue #63): the per-project linked view into the global
# content-addressed store, and the optional hermetic copy from `ludic vendor`. Both
# are regenerated by `ludic get` / `ludic vendor` — package.ludic + package.lock.ludic
# are the tracked source of truth, so these stay out of the tree.
ludic_modules/
vendor/

# editor toolchain build artifacts
tools/editors/vscode/node_modules/
tools/editors/vscode/*.vsix
tools/editors/jetbrains/.gradle/
tools/editors/jetbrains/build/
tools/editors/jetbrains/.kotlin/

# IntelliJ plugin SDK sandbox (tools/editors/jetbrains)
.intellijPlatform/
.idea/

# macOS Finder metadata
.DS_Store
**/.DS_Store

# Python bytecode cache from the docgen / release tooling
__pycache__/
*.pyc

# Release artifacts produced by `ludic-dev release`
/dist/

# Build/release tarballs anywhere in the tree. `git -C <repo> archive -o foo.tgz`
# resolves -o relative to the repo, not the caller's directory, so a stray
# archive lands in the root and a blanket `git add -A` will commit it.
*.tar.gz
*.tgz

# The CC0 Poly Haven downloads are fetched, not committed (`ludic-dev fetch-assets`
# reads the manifest that ships with the renderer, packages/ludic.render3d/assets.manifest,
# so a game outside this repository fetches the same set with `ludic assets`).
assets/polyhaven/hdri/
assets/polyhaven/textures/
assets/polyhaven/models/
# `ludic run` beside an example writes its binary into a build/ there
examples/**/build/

# a package native/build.sh writes its objects under the package (phase 15)
packages/*/build/