diff options
author | Alex Turbov <i.zaufi@gmail.com> | 2018-05-07 20:47:28 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2018-05-11 13:28:44 (GMT) |
commit | f739752ad6f2d661148faa3691189db9251d34b6 (patch) | |
tree | 6e36e2c344db3c659874ea06bd5a3bfdc8c5a104 /CMakeCPack.cmake | |
parent | dd43e6fe895ab84206cab126699e7db7007cc688 (diff) | |
download | CMake-f739752ad6f2d661148faa3691189db9251d34b6.zip CMake-f739752ad6f2d661148faa3691189db9251d34b6.tar.gz CMake-f739752ad6f2d661148faa3691189db9251d34b6.tar.bz2 |
CPack: Add NuGet support
Create a CPack generator that uses `nuget.exe` to create packages:
https://docs.microsoft.com/en-us/nuget/what-is-nuget
NuGet packages could be easily produced from a `*.nuspec` file (running
`nuget pack` in the directory w/ the spec file). The spec filename does
not affect the result `*.nupkg` name -- only `id` and `version` elements
of the spec are used (by NuGet).
Some implementation details:
* Minimize C++ code -- use CMake script do to the job. It just let the
base class (`cmCPackGenerator`) to preinstall everything to a temp
directory, render the spec file and run `nuget pack` in it, harvesting
`*.nupkg` files...;
* Ignore package name (and use default paths) prepared by the base class
(only `CPACK_TEMPORARY_DIRECTORY` is important) -- final package
filename is a responsibility of NuGet, so after generation just scan the
temp directory for the result `*.nupkg` file(s) and update
`packageFileNames` data-member of the generator;
* The generator supports _all-in-one_ (default), _one-group-per-package_
and _one-component-per-package_ modes.
Diffstat (limited to 'CMakeCPack.cmake')
0 files changed, 0 insertions, 0 deletions