3426db05b9
* [scripts-audit rollup] PR #16419 * pull the cmake doc comment parsing out into its own function * support cmake helper ports * add real support for deprecation, as opposed to ad-hoc * [scripts-audit rollup] PR #16192 * add a z_ in front of internal functions * move internal functions out set feature_vars again in parent scope * [scripts-audit rollup] PR #16309 Audit vcpkg_copy_pdbs * [scripts-audit rollup] PR #16304 * Fix usage, documentation * [scripts-audit rollup] PR #16393 * [scripts-audit rollup] PR #16377 Deprecate `vcpkg_*_cmake` in favor of `vcpkg_cmake_*` from the `vcpkg-cmake` port, as well as `vcpkg_fixup_cmake_targets` in favor of `vcpkg_cmake_config_fixup` from the `vcpkg-cmake-config` port.
1.4 KiB
vcpkg_cmake_build
The latest version of this document lives in the vcpkg repo.
Build a cmake project.
vcpkg_cmake_build(
[TARGET <target>]
[LOGFILE_BASE <base>]
[DISABLE_PARALLEL]
[ADD_BIN_TO_PATH]
)
vcpkg_cmake_build builds an already-configured cmake project.
You can use the alias [vcpkg_cmake_install()] function
if your CMake build system supports the install TARGET,
and this is something we recommend doing whenever possible.
Otherwise, you can use TARGET to set the target to build.
This function defaults to not passing a target to cmake.
LOGFILE_BASE is used to set the base of the logfile names;
by default, this is build, and thus the logfiles end up being something like
build-x86-windows-dbg.log; if you use vcpkg_cmake_install,
this is set to install, so you'll get log names like install-x86-windows-dbg.log.
For build systems that are buggy when run in parallel,
using DISABLE_PARALLEL will run the build with only one job.
Finally, ADD_BIN_TO_PATH adds the appropriate (either release or debug)
bin/ directories to the path during the build,
such that executables run during the build will be able to access those DLLs.