-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
Qt Creator 4.1.0
-
None
-
3992c478749a2256f13016a74200fc9d73158507
jom /k runs dependant targets after a failed dependency. This does not match what gmake -k or nmake /k are doing and it does not make sense: in the best case, the dependant target will also fail, in the worst case, it will produce a corrupt result.
Consider the following makefile:
foo: echo foo cmd /c exit 1 bar: foo echo bar
>nmake /F test.make /K bar
Microsoft (R) Program Maintenance Utility Version 14.00.23918.0
Copyright (C) Microsoft Corporation. All rights reserved.
echo foo
foo
cmd /c exit 1
NMAKE : warning U4010: 'foo' : build failed; /K specified, continuing ...
NMAKE : warning U4011: 'bar' : not all dependents available; target not built
This is what I expect.
>jom /F test.make /K bar
jom 1.1.1 - empower your cores
echo foo
foo
cmd /c exit 1
jom: E:\brunodf\jom\test.make [foo] Error 1
echo bar
bar
Running target bar is unexpected here.