#Cmake install dependencies mac
At its core, it is a CMake wrapper around the NuGet command-line interface (NuGet CLI), that "provides all NuGet capabilities on Windows, provides most features on Mac and Linux when running under Mono". ScopeĬMakeNuGetTools aims to be the cross-platform NuGet package management solution for CMake-based C/C++ projects. See (which is used from CMakeLists.txt) as a simple example in the root directory of this repository.
#Cmake install dependencies install
See test project subdirectories under the tests subdirectory in this repository for example uses of these functions.Ĭalling nuget_merge_nuspec_files and nuget_pack is primarily intended to be done outside of CMakeLists.txt files: they can be called from CMake script files (on top of your project descriptor CMakeLists.txt files) driving the build system generation, triggering the actual build and install of the project, etc. The nuget_generate_nuspec_files function is especially to be used from CMakeLists.txt files only, as it calls CMake's built-in file(GENERATE) in the end: output files are only written after processing all of a project's CMakeLists.txt files. The nuget_initialize, nuget_add_dependencies, nuget_generate_nuspec_files functions, and some helper functions are primarily intended to be used from a CMakeLists.txt file. (Every other script file outside the cmake subdirectory in the CMakeNuGetTools repository is currently only used for stand-alone testing.) The NuGetTools.cmake script currently includes all other required CMakeNuGetTools CMake scripts, so that you can call any of the provided nuget_*() functions after including NuGetTools.cmake in your CMake scripts. Only relative locations within the cmake subdirectory need to be retained if you copy over the scripts. No specific location within your repository is required for the CMakeNuGetTools CMake scripts found under the cmake subdirectory in this repository in order to work properly. ) in your CMake scripts.ĬMakeNuGetTools can be thought of as an intrinsic part of the build scripting of your CMake-based projects, and as such it is preferably present in your repositories as a copy. Alternatively, you can use CMake's find_program(NUGET_COMMAND.Of course, you can also provide an absolute path to nuget.exe when setting the NUGET_COMMAND cache variable.when executing the CMake CLI: cmake -DNUGET_COMMAND=nuget.exe. If nuget.exe is within your PATH environment, you can set the value of the cache variable to nuget.exe, e.g.Set the NUGET_COMMAND CMake cache variable to reference the previously installed NuGet CLI. If you have a CMake script file from which you want to use the NuGetTools.cmake, you can also use an include() adjusting the given path. CMAKE_OUTPUT_DIR $/scripts/CMakeNuGetTools/NuGetTools.cmake")
0 kommentar(er)
