Alois Wohlschlager
21fc0ddce5
Currently, a bunch of documentation is generated by embedding parts of it in the nix executable, getting it out again by running it, and then postprocessing the output. This is bad, since it creates a pointless dependency of the documentation on the executable, and also makes documentation generation impossible when cross-compiling. Instead, both the code and the documentation should be generated from data, see https://git.lix.systems/lix-project/lix/issues/292 . Here we start applying this approach to the experimental and deprecated features, which are done in one go since the technical implementation is very similar. Of course, the actual benefits are not realised yet, since the offending pattern is used in several more places. These will be fixed later. Change-Id: I4c802052cc7e865c61119a34b8f1063c4decc9cb
42 lines
609 B
Plaintext
42 lines
609 B
Plaintext
outputs/
|
|
|
|
# GNU Global
|
|
GPATH
|
|
GRTAGS
|
|
GSYMS
|
|
GTAGS
|
|
|
|
# ccls
|
|
/.ccls-cache
|
|
|
|
# auto-generated compilation database
|
|
compile_commands.json
|
|
rust-project.json
|
|
|
|
result
|
|
result-*
|
|
|
|
.vscode/
|
|
.direnv/
|
|
|
|
# clangd and possibly more
|
|
.cache/
|
|
|
|
# Mac OS
|
|
.DS_Store
|
|
|
|
# ClangBuildAnalyzer output, see maintainers/buildtime_report.sh
|
|
buildtime.bin
|
|
|
|
.envrc.local
|
|
# We generate this with a Nix shell hook
|
|
/.pre-commit-config.yaml
|
|
/.nocontribmsg
|
|
/release
|
|
|
|
# Rust build files when using Cargo (not actually supported for building but it spews the files anyway)
|
|
/target/
|
|
|
|
# Python compiled files from the code generators and test suite
|
|
*.pyc
|