CPSC 480 Build Files
Across
- 1. The example platform toolchain file for gcc is _____
- 4. The main presets filename is _____
- 7. Literal gcc/clang flag to enable c++17
- 8. Related tool for running tests with cmake
- 11. An optional, developer-specific presets filename is _____
- 18. Make directive to declare targets that are not real files
- 19. The build configuration file for vcpkg builds is _____
- 21. Modern per-target way to request language features in cmake is _____ (full comand including underscores)
- 24. MSVC warning flag used in the example
- 25. Always use a build _____; don’t type raw compiler commands for real work
- 26. The build where the build-generated files (object code and executables) are in the source directory with the source files is an ______ _____ _____
- 27. Creating a _____ is challenging
- 28. Build files are both _____ and _____ over a project’s lifetime
- 29. Things don’t always work the same on all platforms, so you have to _____
Down
- 2. Feature to require c++17 _____
- 3. Most build languages are ______ as opposed to imperative
- 5. The cmake command to create a custom target, such as “run”, is ______ (full name including underscores)
- 6. The cmake-provided target that copies files to the system is _____
- 9. Much platform-specific config can now live in a json format in cmake _____ files
- 10. Makefiles do not easily handled multiple _____
- 12. The command `cmake --help` shows you a list of _____ at the end of the output
- 13. _____ is a build-file generator that can target many platforms and environments
- 14. Literal MSVC flag to enable c++17
- 15. Prefer an _____-_____-_____ build
- 16. A variation of install that removes symbols is _____/_____
- 17. Make is _____ complete
- 18. In a Makefile, you must list all _____ include files (i.e., .h and .hpp files)
- 20. Makefiles do not easily handle multiple build _____
- 22. Related tool for packaging/installers with cmake
- 23. Standard gcc/clang warnings flag used in the example