You are right that dotnet publish automatically does everything dotnet build already does. In most cases – as in your scenario mentioned in the question – that means an additional dotnet build is not necessary. Do note that you can dotnet build a solution, but should only dotnet publish individual project files. Publishing solutions likely … Read more
Just found it from Appendix D. Gradle Command Line. The answer is -p <your project directory>, which defaults to the current directory.
I was actually trying to do this today, and I found typing this into the CLisp REPL worked: (EXT:SAVEINITMEM “executable.exe” :QUIET t :INIT-FUNCTION ‘main :EXECUTABLE t :NORC t) where main is the name of the function you want to call when the program launches, :QUIET t suppresses the startup banner, and :EXECUTABLE t makes a … Read more
You’ve got a thorough listing of the options available, but this question will not have a clear answer. My personal recommendation is also to use ocamlbuild. The myocamlbuild.ml file provided here is a good start. It will allow you to easily compile projects that depend on various libraries. I don’t think it handles the case … Read more
Update as of version 2.23 of Parameterized Trigger Plugin: With version 2.23+ behavior changed (thanks AbhijeetKamble for pointing out). Any parameter that is being passed by Predefined Parameters section of calling (build) job has to exist in the called (deploy) job. Furthermore, the restrictions of called job’s parameters apply, so if the called job’s parameter … Read more
There is no automated tool that will convert an arbitrary build system from autotools to cmake. I have converted a few moderately large projects manually. I like to create one CMakeLists.txt file for each set of configure.ac and/or Makefile.am file, to ease the conversion from autotools to cmake. Sadly, this manual approach requires developing an … Read more
Disabling the built-in rules is done by writing an empty rule for .SUFFIXES: .SUFFIXES: Having erased the built-in rules, I’m not sure that erasing the built-in variables helps you much more than just remembering to set them yourself or not use them, but you could use something like $(foreach V, $(shell make -p -f/dev/null 2>/dev/null … Read more
You can set the GRADLE_USER_HOME environment variable, gradle.user.home system property, or –gradle-user-home command line parameter.
The reason given is actually a huge benefit. Builds that go to QA should only ever come from a system that builds only from the repository. This way build packages are reproducible and traceable. Developers manually building code for anything except their own testing is dangerous. Too much risk of stuff not getting checked in, … Read more
There are two types of generators: single-configurations and multi-configurations. Single configurations Make-like generators: Unix Makefiles, NMake Makefiles, MinGW Makefiles, … You set the configuration type in the generate step: cmake -H. -B_builds/Debug -DCMAKE_BUILD_TYPE=Debug “-GUnix Makefiles” In this case, the build step is always Debug: > cmake –build _builds/Debug /usr/bin/c++ -g … > cmake –build _builds/Debug … Read more