Autocmake¶
- FAQ for developers
- Which files do I need to edit?
- Autocmake does not do feature X - I really need feature X and a setup flag –X
- How can I get a setup flag –X that toggles a CMake variable?
- Can I change the name of the setup script?
- Can I prevent Autocmake from creating any front-end setup script?
- In CMake I can do feature X - can I do that also with Autocmake?
- Should I include and track also files generated by Autocmake in my repository?
- The update.py script is overwriting my CMakeLists.txt and setup, isn’t this bad?
- But I need to manually edit and customize CMakeLists.txt and setup every time I run update.py!?
- Where is a good place to list my sources and targets?
- How can I do some more sophisticated validation of setup flags?
- Bootstrapping a new project
- Configuring autocmake.yml
- Example hello world project
- Customizing CMake modules
- Updating CMake modules
- Interpolation
- Module reference
- boost.cmake
- cc.cmake
- ccache.cmake
- code_coverage.cmake
- custom_color_messages.cmake
- cxx.cmake
- default_build_paths.cmake
- definitions.cmake
- export_header.cmake
- fc.cmake
- fc_optional.cmake
- git_info.cmake
- googletest.cmake
- int64.cmake
- accelerate.cmake
- acml.cmake
- atlas.cmake
- blas.cmake
- cblas.cmake
- goto.cmake
- lapack.cmake
- lapacke.cmake
- math_libs.cmake
- mpi.cmake
- omp.cmake
- profile.cmake
- python_interpreter.cmake
- python_libs.cmake
- safeguards.cmake
- save_flags.cmake
- src.cmake
- version.cmake