Add support for cmake/ninja --install
See original GitHub issueHi,
I am currently using the action to build my project and everything works fine. However, my project does not only contain source files that need to be build, but rather uses install
to put everything in place (e.g. raw files, artifacts, headers, etc.). It would be quite convenient, if run-cmake could be configured to automatically run ninja install
or cmake --install
after a successful build. For ninja, the install directory is stored in the CMakeSettings.json
file. The action could treat it just as it does with the buildRoot
directory (i.e. ignore and set to a default; maybe make it configurable).
Do you think this is possible?
Thanks and regards, Carsten.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Ninja — CMake 3.25.1 Documentation
Generates build.ninja files. A build.ninja file is generated into the build tree. Use the ninja program to build the project through the all...
Read more >The Ninja build system
A widely used meta-build system that can generate Ninja files on Linux as of CMake version 2.8.8. Newer versions of CMake support generating...
Read more >CMake Ninja Combo: The Gist
Install the latest version of Python and open a Visual Studio x64 native tools command prompt. Issue the above two commands, the first...
Read more >Add support for the Ninja CMake generator · Issue #8
Hm, build seems to be able to saturate 16 threads (make -j16), don't think there is too much to gain there. Switching to...
Read more >Integrate custom C/C++ build systems using Ninja ...
Learn about experimental C/C++ Ninja build system support. ... CMake can generate projects for Android, iOS, and other platforms from a ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FWIW, you can accomplish this using the
run-cmake
action by specifying the build target:@Aschratt yes, it make sense to add a option similar to
buildWithCMake
, calledinstallWithCMake
, with default set to false. For the time being, the solution is to run cmake --install in a run step, assuming the cwd is the right one e.g.: