On Fri, Nov 18, 2011 at 10:02:54AM +0100, Nicolas Desprès wrote: > On Wed, Nov 16, 2011 at 3:05 PM, OKUMURA Yuki <m...@cltn.org> wrote: > > > (Sorry Bill, i repost here..) > > > > 2011/11/16 Bill Hoffman <bill.hoff...@kitware.com>: > > - snip - > > > What type of evolution will Ninja need? I suppose it could use cmake > > > scripts and exectue_process which can do && type things pretty easy. > > > > Why not insert "cmd /c" everywhere? :) > > Anyway, i had tried this in early this month, > > > > https://github.com/okuoku/CMake/commit/db19df03606684f313c9e86b313218feee9cce3f > > but it didn't work well.
How so? Was there an escaping issue? The cmd.exe documentation seems to indicate that this will work. http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ntcmds_shelloverview.mspx#EBG > > > > I think almost all use of "&&" is just "chdir /d $workdir && > > compile/link-command." So, adding $workdir > > specifier to target syntax of Ninja might work for many cases. > > > > That's right. I just had a look at the build.ninja file generated by the > Ninja Generator and it actually uses && only for changing the working > directory. I will suggest a patch to Ninja to support working directory > for each build statement. That's not the only thing that the Ninja generator uses && for. It also uses && to prepend/append PRE_BUILD, PRE_LINK and POST_BUILD commands to the link command, and to concatenate multiple custom command lines. Thanks, -- Peter -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
