There might be something I'm doing wrong, but hey, I've tried everything.
I want my command to start several background exes, keep them open, and finish the build.
That way, I can start the exes, modify js files and test away.
To do that, no problem, I call a bat that STARTs all my exes:
.atom-build.json:
I've tried every possible way. Starting the bat, CALLing it, adding /C flag, same in the bat file, whatever.
Any way, the result is the same: The build keeps running until I've closed every single background application; making it unusable for other targets.
My assumption is that every way proposed by windows commands will spawn other exes, but considered as children of the root process, which will not die until they all die, and will not mark the build as finished until then.
Is there a way to do so? I would like it very very much. Thank you!
There might be something I'm doing wrong, but hey, I've tried everything.
I want my command to start several background exes, keep them open, and finish the build. That way, I can start the exes, modify js files and test away.
To do that, no problem, I call a bat that STARTs all my exes: .atom-build.json:
go.bat:
I've tried every possible way. Starting the bat, CALLing it, adding /C flag, same in the bat file, whatever.
Any way, the result is the same: The build keeps running until I've closed every single background application; making it unusable for other targets.
My assumption is that every way proposed by windows commands will spawn other exes, but considered as children of the root process, which will not die until they all die, and will not mark the build as finished until then.
Is there a way to do so? I would like it very very much. Thank you!