c92b52537c
ninja has a single build file which avoided issues if multiple targets depend on same files. But Unix Makefiles generator user recursive make which requires each ADD_CUSTOM_COMMAND to have only one target depending on them. Then makefile generator also has stupid rule that it touches all secundary output files if primary file has been updated. It was surprising hard to find a version that actually works correctly for both issues. Solution is using BYPRODUCTS and refactoring command and target dependencies. As a bonus this change now allows build to work from source tarball if the tarball includes git-describe.h. |
||
|---|---|---|
| CMake | ||
| build | ||
| depends | ||
| dfhack-config | ||
| docs | ||
| library | ||
| package | ||
| plugins | ||
| reversing | ||
| scripts@801499ab67 | ||
| test | ||
| travis | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| .ycm_extra_conf.py | ||
| CMakeLists.txt | ||
| Contributing.rst | ||
| LICENSE.rst | ||
| README.html | ||
| README.md | ||
| conf.py | ||
| dfhack.init-example | ||
| index.rst | ||
| onLoad.init-example | ||
README.md
DFHack Readme
DFHack is a Dwarf Fortress memory access library, distributed with scripts and plugins implementing a wide variety of useful functions and tools.
The full documentation is available online here,
from the README.html page in the DFHack distribution, or as raw text in the ./docs folder.
If you're an end-user, modder, or interested in contributing to DFHack -
go read those docs.
If that's unclear or you need more help, try the Bay12 forums thread or the #dfhack IRC channel on freenode.