[cmake-developers] -GNinja on Windows

Peter Kümmel syntheticpp at gmx.net
Tue Jun 12 08:42:07 EDT 2012


On 12.06.2012 13:47, Amine Khaldi wrote:
>> One of my last changes was to replaces back slashes with slashes
>> exactly because of "\../../" problems. Have you used cl and
>> recent next?
> With cl and recent next:
>
> * Our host tools (the host-tools folder) basically get rebuilt everytime
> you run ninja, and -d explain suggests "x86 is dirty" and "/Windows
> Kits/8.0/include/shared/sal.h is dirty"...etc because we end up with
> entries like "C:/Program\ Files\ (x86)/Windows\
> Kits/8.0/include/shared/ConcurrencySal.h" and "C:/Program\ Files\
> (x86)/Windows\ Kits/8.0/include/shared/sal.h" in the .d files.

Fixed. It was because of the parentheses. Such paths will be ignored.

>
> * As to ros itself, ntoskrnl produces a correct "ninja: no work to do."
> when you rebuild and also tracks this
> "E:/reactos/ntoskrnl/include/../mm/ARM3/miarm.h" correctly if you alter
> it (leading to the recompilation of the dependent files).
>
> * Here we also lack the dependency tracking of the includes inside rc files.

rc doesn't support something like /showInclude. Only idea I have to feed cl
with the .rc file and to hope it prints the include paths before it breaks.
But I don't know if it worth the effort.

>
>
> With gcc (windows) and recent next:
>
> * Our host tools (the host-tools folder) basically get rebuilt everytime
> you run ninja, and -d explain suggests "psdk/guiddef.h is dirty"
> (because of e:\reactos\include\host/../psdk/guiddef.h in the .d files)
> and "reactos/wine/rpcfc.h is dirty" (because of
> e:\reactos\include\host/wine/../../reactos/wine/rpcfc.h)... etc.
> * As to ros itself, ntoskrnl gets recompiled everytime, because of
> entries like "e:\reactos\ntoskrnl\include/../kdbg/kdb.h" and
> "e:\reactos\ntoskrnl\include/../mm/ARM3/miarm.h"... etc.

Fixed by using slashes.

>
> Regards,
> Amine.
> --
>
> 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
>



More information about the cmake-developers mailing list