Hi Brad,
> For `cmake --build` we already need to detect the generator used
> for the build tree in order to ask it to construct the appropriate
> command line. For the VS generator we could directly run the same
> check that ZERO_CHECK would run in order to decide whether to regen
> the build
I can't commit to the gitlab , it says something regarding no disk space.
$ git push
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 2.36 KiB | 0 bytes/s, done.
Total 5 (delta 4), reused 0 (delta 0)
remote:
Thank you Brad. I took the aggressive way and completely wiped the environment
inside the debugged process. For those anyone wishing to do something similar,
here’s what I’ve done:
I wrote a PowerShell oneliner:
gci Env: | foreach { $_.Name + "=" + $_.Value } | Out-File -FilePath
On 09/16/2016 06:32 AM, csiga.b...@aol.com wrote:
> Now it’s only up to me to understand the entire process of Makefile
> generation.
> Global/Local Generators, LocalMakeFileGenerator3 (does 3 correspond to the
> third layer of makefiles? If yes, where is 2?)
The 3 is the third generation of
On 09/16/2016 03:37 AM, Yves Frederix wrote:
> This would work, but it would make all builds using 'cmake --build'
> more verbose as before actually starting the msbuild-build, this would
> always print an often large number of lines like:
>
> CMake does not need to re-run because
