[RFC] Send output of building setup to stderr (fixes #1410)#1423
Conversation
|
can someone review 5f9c75e ? I'm unsure about it. |
|
one of my motivations to refactor runIn, callProcess, callProcess' was that they were taking arguments in different order, and that it was harder to explore the code without a common CMD prefix. |
|
5f9c75e seems good to me. I have the following nitpicks:
The other commits look good too, thanks for working on this! For some reason the build is failing in the windows CI: https://ci.appveyor.com/project/snoyberg/stack/build/1.0.546#L766 |
43293f5 to
5c7ba6e
Compare
|
@mgsloan I rebased it cleanly on master, and tweaked it according to your comments |
|
Looks like you might have accidentally added It's failing to build on Windows because there is some CPP in |
|
@borsboom thanks |
|
Changes look good to me, One last thing before merging: Can you please use |
…ake a Cmd arg introduce CMD data type add runCmd' following callProcess' model actually fixes commercialhaskell#1410 rename CMD -> Cmd move Cmd to System.Process.Run clean redundant imports remove test.dot and test.html fix callProcess call on windows in Stack.Exec
86189e4 to
332636b
Compare
|
I've squashed it all on one single commit |
|
Thanks! |
[RFC] Send output of building setup to stderr (fixes #1410)
this PR
runIntorunCmdrunCmd'function taking and extra(CreateProcess -> CreateProcess)paramrunCmd' (\cp -> cp { std_out = UseHandle stderr })ingetSetupExedata CMD = CMD directoryToRunIn commandToRun envOverride commandLineArgumentsrunIn,callProcess,callProcess'to take a CMD arg to ease code exploration, and argument passing