Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-19 Thread Nicolas Desprès
2012/2/19 Eric Noulard 

> Le 19 février 2012 15:19, Nicolas Desprès  a
> écrit :
> >
> > Thanks for this Peter.  I have just tried the new stage/ninja-generator
> > branch with spaces in both the source and the binary directory and I got
> > this result for the test suite:
> >
> >  The following tests FAILED:
> > 83 - CPackComponents (Failed)
> > 217 - CMake.CheckSourceTree (Failed)
> >
> > Note that on my Linux box:
> > - CMake.CheckSourceTree always fail even on the master branch (I never
> tried
> > to understand why).
>
> Because you should have some local modification in the source tree.
> Try:
> ctest -V -R CMake.CheckSourceTree
>
> and you'll possibly get an explanation like:
> 232: additions='0'
> 232: conflicts='0'
> 232: modifications='0'
> 232: nonadditions='1'
> ...
> 232: CMake Error at CheckSourceTreeTest.cmake:422 (message):
> 232:   test fails: local source tree non-additions: use git add before
> committing,
> 232:   or remove the files from the source tree
>
>
True I had some untracked files. Thanks it works now :)


>  > - CPackComponents fails only when there are spaces but the Unix
> Makefiles
> > generator has the same issue.
>
> I think this should not happen, normally CPack generators that cannot
> handle space in build tree (like CPackRPM) should be filtered out.
>
> In order to know the culprit same method applies here:
> ctest -V -R "^CPackComponents$"
>
> (you can do ctest -V -R CPackComponents
>  but you'll get more tests)
>

I open a new discussion thread "CPackComponents fails with spaces in paths"
cause it is off-topic.

Thanks,

-- 
Nicolas Desprès
--

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

Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-19 Thread Eric Noulard
Le 19 février 2012 15:19, Nicolas Desprès  a écrit :
>
> Thanks for this Peter.  I have just tried the new stage/ninja-generator
> branch with spaces in both the source and the binary directory and I got
> this result for the test suite:
>
>  The following tests FAILED:
> 83 - CPackComponents (Failed)
> 217 - CMake.CheckSourceTree (Failed)
>
> Note that on my Linux box:
> - CMake.CheckSourceTree always fail even on the master branch (I never tried
> to understand why).

Because you should have some local modification in the source tree.
Try:
ctest -V -R CMake.CheckSourceTree

and you'll possibly get an explanation like:
232: additions='0'
232: conflicts='0'
232: modifications='0'
232: nonadditions='1'
...
232: CMake Error at CheckSourceTreeTest.cmake:422 (message):
232:   test fails: local source tree non-additions: use git add before
committing,
232:   or remove the files from the source tree

> - CPackComponents fails only when there are spaces but the Unix Makefiles
> generator has the same issue.

I think this should not happen, normally CPack generators that cannot
handle space in build tree (like CPackRPM) should be filtered out.

In order to know the culprit same method applies here:
ctest -V -R "^CPackComponents$"

(you can do ctest -V -R CPackComponents
 but you'll get more tests)


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
--

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


Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-19 Thread Nicolas Desprès
2012/2/19 Peter Collingbourne 

> On Fri, Feb 17, 2012 at 09:16:31PM +0100, Nicolas Desprès wrote:
> > 2012/2/17 Bill Hoffman 
> >
> > > On 2/17/2012 12:26 PM, Nicolas Desprès wrote:
> > >
> > >>
> > >> I think it is a bug in the generator which do not escape the space
> > >> properly using the $ character as supported by Ninja.
> > >>
> > >> --
> > >> Nicolas Desprès
> > >>
> > >>  Will you be able to fix that?
> > >
> >
> > I think yes. It is just a matter of time. My weekend is already
> overloaded.
> > I'll try to do it. If Peter or someone else in the community comes up
> with
> > a patch before me everybody would be happy :-)
>
> I decided to look into escaping rules this weekend.  Now with the
> code on the ninja-generator branch, CMake can build itself with both
> source and build directories containing spaces, and pass all tests.
> LLVM/Clang can also build with both directory names containing spaces.
>
>
Thanks for this Peter.  I have just tried the new stage/ninja-generator
branch with spaces in both the source and the binary directory and I got
this result for the test suite:

 The following tests FAILED:
 83 - CPackComponents (Failed)
217 - CMake.CheckSourceTree (Failed)

Note that on my Linux box:
- CMake.CheckSourceTree always fail even on the master branch (I never
tried to understand why).
- CPackComponents fails only when there are spaces but the Unix Makefiles
generator has the same issue.

Cheers,

-- 
Nicolas Desprès
--

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

Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-18 Thread Peter Collingbourne
On Fri, Feb 17, 2012 at 09:16:31PM +0100, Nicolas Desprès wrote:
> 2012/2/17 Bill Hoffman 
> 
> > On 2/17/2012 12:26 PM, Nicolas Desprès wrote:
> >
> >>
> >> I think it is a bug in the generator which do not escape the space
> >> properly using the $ character as supported by Ninja.
> >>
> >> --
> >> Nicolas Desprès
> >>
> >>  Will you be able to fix that?
> >
> 
> I think yes. It is just a matter of time. My weekend is already overloaded.
> I'll try to do it. If Peter or someone else in the community comes up with
> a patch before me everybody would be happy :-)

I decided to look into escaping rules this weekend.  Now with the
code on the ninja-generator branch, CMake can build itself with both
source and build directories containing spaces, and pass all tests.
LLVM/Clang can also build with both directory names containing spaces.

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


Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Bill Hoffman

If I edit the build.ninja file directly:

this:
ident21 = /media/Work/My\ Builds/cmake/Utilities/KWIML/test/test.c
to this:
ident21 = /media/Work/My$ Builds/cmake/Utilities/KWIML/test/test.c

Then it does not complain about test.c.  So it seems like the place to 
fix this would be where it rights out the path to the sources and to 
replace the "\ " stuff with "$ ".  Or the place that puts in the "\ " 
and use $ instead of \ to escape the spaces  in the first place.


As a quick hack I tried this:

std::string cmNinjaTargetGenerator::ConvertToNinjaPath(const char *path) 
const

{
  std::string p = this->LocalGenerator->Convert(path,

cmLocalGenerator::HOME_OUTPUT,

cmLocalGenerator::MAKEFILE);
  cmSystemTools::ReplaceString(p, "\\ ", "$ ");
  return p;
}

It got further but got hung up on Docs/ctest.txt.  That is from a custom 
command so it must be calling something else to convert to paths for 
those...


-Bill
--

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


Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Bill Hoffman

On 2/17/2012 5:09 PM, Peter Kümmel wrote:

On 17.02.2012 21:37, Bill Hoffman wrote:

On 2/17/2012 3:16 PM, Nicolas Desprès wrote:



I think yes. It is just a matter of time. My weekend is already
overloaded. I'll try to do it. If Peter or someone else in the community
comes up with a patch before me everybody would be happy :-)

I'll try to do my best.


I could give it a try if you pointed me to the right spot in the code...


Does attached patch help?


Nope:

http://www.cdash.org/CDash/viewBuildError.php?buildid=2015922

-Bill
--

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


Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Nicolas Desprès
On Fri, Feb 17, 2012 at 11:09 PM, Peter Kümmel  wrote:

> On 17.02.2012 21:37, Bill Hoffman wrote:
>
>  On 2/17/2012 3:16 PM, Nicolas Desprès wrote:
>>
>>
>>> I think yes. It is just a matter of time. My weekend is already
>>> overloaded. I'll try to do it. If Peter or someone else in the community
>>> comes up with a patch before me everybody would be happy :-)
>>>
>>> I'll try to do my best.
>>>
>>>  I could give it a try if you pointed me to the right spot in the code...
>>
>
> Does attached patch help?


I don't think so because EncodeLiteral is only called in
WriteCustomCommandBuild to encode the description:

  vars["DESC"] = EncodeLiteral(description);

Plus I think we should keep the description untouched since it is printed
in the terminal. This description is the description of custom command rule
used here in rules.ninja:

rule CUSTOM_COMMAND
  command = $COMMAND
  description = $DESC
  restat = 1

Thanks for the patch anyway.

-- 
Nicolas Desprès
--

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

Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Peter Kümmel

On 17.02.2012 21:37, Bill Hoffman wrote:

On 2/17/2012 3:16 PM, Nicolas Desprès wrote:



I think yes. It is just a matter of time. My weekend is already
overloaded. I'll try to do it. If Peter or someone else in the community
comes up with a patch before me everybody would be happy :-)

I'll try to do my best.


I could give it a try if you pointed me to the right spot in the code...


Does attached patch help?

Peter
diff --git a/Source/cmGlobalNinjaGenerator.cxx b/Source/cmGlobalNinjaGenerator.cxx
index 7ff33ba..190e777 100644
--- a/Source/cmGlobalNinjaGenerator.cxx
+++ b/Source/cmGlobalNinjaGenerator.cxx
@@ -77,6 +77,7 @@ std::string cmGlobalNinjaGenerator::EncodeLiteral(const std::string &lit)
 {
   std::string result = lit;
   cmSystemTools::ReplaceString(result, "$", "$$");
+  cmSystemTools::ReplaceString(result, " ", "$ ");
   return result;
 }
 
--

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

Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Nicolas Desprès
2012/2/17 Nicolas Desprès 

>
>
> 2012/2/17 Bill Hoffman 
>
>> On 2/17/2012 3:16 PM, Nicolas Desprčs wrote:
>>
>>
>>> I think yes. It is just a matter of time. My weekend is already
>>> overloaded. I'll try to do it. If Peter or someone else in the community
>>> comes up with a patch before me everybody would be happy :-)
>>>
>>> I'll try to do my best.
>>>
>>>  I could give it a try if you pointed me to the right spot in the code...
>
>
> I think the first place to look at is cmGlobalNinjaGenerator.cxx. There
> are a bunch of class methods there that are used to write the statements in
> the .ninja files.
>
> Look at WriteBuild() in particular. Many others are convenient methods
> based on this one. So the escaping logic should happen there. "build"
> statements in ninja are where most of the path are written.
> Some problem may arise from WriteRule() since the path to the command is
> written by it.
>
> Also there are:
>   static std::string EncodeIdent(const std::string &ident, std::ostream
> &vars);
>   static std::string EncodeLiteral(const std::string &lit);
>
> which I don't really know since I haven't written them and they are not
> documented. Peter did. But their name are pretty explicit and their code
> trivial.
>
> I think we should add an EncodePath() method to follow the same logic and
> use it in WriteBuild() and WriteRule().
>
> In WriteBuild(), arguments like ouputs, explictDeps, implicitDeps,
> orderOnlyDeps must be encoded. The tricky part would be that some part of
> the value of the "variables" arguments (which is a hash_map) must be
> encoded because they may be a white space sparated list of word which may
> contains some paths...
>

Just to be clearer, "outputs", "explicitDeps", "implicitDeps" and
"orderOnlyDeps" are all a list of paths (types are declared in
cmNinjaTypes.h) so each item of the list must be encoded.

A "build" statements look like this (using the argument name of WriteBuild):

comment
build outputs: rule explicitDeps | implicitDeps || orderOnlyDeps
  variables


>
> For exemple look at this part of the build.ninja file generated for cmake:
>
> build Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testXMLParser.cxx.o:
> CXX_COMPILER ../Tests/CMakeLib/testXMLParser.cxx || Source/libCMakeLib.a
>   DEFINES = -DLIBARCHIVE_STATIC
>   FLAGS = -Wall  -g -IUtilities -I../Utilities -ITests/CMakeLib -ISource
> -I../Source
>
> or this one:
>
> # Link the executable Tests/CMakeLib/CMakeLibTests
> build Tests/CMakeLib/CMakeLibTests: CXX_EXECUTABLE_LINKER
> Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/CMakeLibTests.cxx.o
> Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testGeneratedFileStream.cxx.o
> Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testSystemTools.cxx.o
> Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testUTF8.cxx.o
> Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testXMLParser.cxx.o
> Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testXMLSafe.cxx.o |
> Source/libCMakeLib.a Source/kwsys/libcmsys.a /usr/lib/libexpat.so
> Utilities/cmlibarchive/libarchive/libcmlibarchive.a /usr/lib/libz.so
> Utilities/cmbzip2/libcmbzip2.a Utilities/cmcompress/libcmcompress.a
> /usr/lib/libcurl.so
>   FLAGS = -Wall  -fPIC
>   LINK_LIBRARIES = -rdynamic Source/libCMakeLib.a Source/kwsys/libcmsys.a
> -ldl -lexpat Utilities/cmlibarchive/libarchive/libcmlibarchive.a -lz
> Utilities/cmbzip2/libcmbzip2.a Utilities/cmcompress/libcmcompress.a -lcurl
>   POST_BUILD = :
>   PRE_LINK = :
>
> In this case I think the encoding should happen before the call to
> WriteBuild when the "variables" argument is built because WriteBuild would
> not have enough information to figure out which part of the variable value
> is a path or not, specially for things like: "-I../Utilities"
>
> Hope this helps,
> Cheers,
> -Nico
>
>


-- 
Nicolas Desprès
--

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

Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Nicolas Desprès
2012/2/17 Bill Hoffman 

> On 2/17/2012 3:16 PM, Nicolas Desprčs wrote:
>
>
>> I think yes. It is just a matter of time. My weekend is already
>> overloaded. I'll try to do it. If Peter or someone else in the community
>> comes up with a patch before me everybody would be happy :-)
>>
>> I'll try to do my best.
>>
>>  I could give it a try if you pointed me to the right spot in the code...


I think the first place to look at is cmGlobalNinjaGenerator.cxx. There are
a bunch of class methods there that are used to write the statements in the
.ninja files.

Look at WriteBuild() in particular. Many others are convenient methods
based on this one. So the escaping logic should happen there. "build"
statements in ninja are where most of the path are written.
Some problem may arise from WriteRule() since the path to the command is
written by it.

Also there are:
  static std::string EncodeIdent(const std::string &ident, std::ostream
&vars);
  static std::string EncodeLiteral(const std::string &lit);

which I don't really know since I haven't written them and they are not
documented. Peter did. But their name are pretty explicit and their code
trivial.

I think we should add an EncodePath() method to follow the same logic and
use it in WriteBuild() and WriteRule().

In WriteBuild(), arguments like ouputs, explictDeps, implicitDeps,
orderOnlyDeps must be encoded. The tricky part would be that some part of
the value of the "variables" arguments (which is a hash_map) must be
encoded because they may be a white space sparated list of word which may
contains some paths...

For exemple look at this part of the build.ninja file generated for cmake:

build Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testXMLParser.cxx.o:
CXX_COMPILER ../Tests/CMakeLib/testXMLParser.cxx || Source/libCMakeLib.a
  DEFINES = -DLIBARCHIVE_STATIC
  FLAGS = -Wall  -g -IUtilities -I../Utilities -ITests/CMakeLib -ISource
-I../Source

or this one:

# Link the executable Tests/CMakeLib/CMakeLibTests
build Tests/CMakeLib/CMakeLibTests: CXX_EXECUTABLE_LINKER
Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/CMakeLibTests.cxx.o
Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testGeneratedFileStream.cxx.o
Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testSystemTools.cxx.o
Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testUTF8.cxx.o
Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testXMLParser.cxx.o
Tests/CMakeLib/CMakeFiles/CMakeLibTests.dir/testXMLSafe.cxx.o |
Source/libCMakeLib.a Source/kwsys/libcmsys.a /usr/lib/libexpat.so
Utilities/cmlibarchive/libarchive/libcmlibarchive.a /usr/lib/libz.so
Utilities/cmbzip2/libcmbzip2.a Utilities/cmcompress/libcmcompress.a
/usr/lib/libcurl.so
  FLAGS = -Wall  -fPIC
  LINK_LIBRARIES = -rdynamic Source/libCMakeLib.a Source/kwsys/libcmsys.a
-ldl -lexpat Utilities/cmlibarchive/libarchive/libcmlibarchive.a -lz
Utilities/cmbzip2/libcmbzip2.a Utilities/cmcompress/libcmcompress.a -lcurl
  POST_BUILD = :
  PRE_LINK = :

In this case I think the encoding should happen before the call to
WriteBuild when the "variables" argument is built because WriteBuild would
not have enough information to figure out which part of the variable value
is a path or not, specially for things like: "-I../Utilities"

Hope this helps,
Cheers,
-Nico
--

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

Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Bill Hoffman

On 2/17/2012 3:16 PM, Nicolas Desprès wrote:



I think yes. It is just a matter of time. My weekend is already
overloaded. I'll try to do it. If Peter or someone else in the community
comes up with a patch before me everybody would be happy :-)

I'll try to do my best.


I could give it a try if you pointed me to the right spot in the code...

-Bill

--

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


Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Nicolas Desprès
2012/2/17 Bill Hoffman 

> On 2/17/2012 12:26 PM, Nicolas Desprès wrote:
>
>>
>> I think it is a bug in the generator which do not escape the space
>> properly using the $ character as supported by Ninja.
>>
>> --
>> Nicolas Desprès
>>
>>  Will you be able to fix that?
>

I think yes. It is just a matter of time. My weekend is already overloaded.
I'll try to do it. If Peter or someone else in the community comes up with
a patch before me everybody would be happy :-)

I'll try to do my best.

Cheers,
-Nico
--

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

Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Bill Hoffman

On 2/17/2012 12:26 PM, Nicolas Desprès wrote:


I think it is a bug in the generator which do not escape the space
properly using the $ character as supported by Ninja.

--
Nicolas Desprès


Will you be able to fix that?


Thanks.

-Bill
--

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


Re: [cmake-developers] ninja spaces in the path do not work on linux

2012-02-17 Thread Nicolas Desprès
On Wed, Feb 15, 2012 at 9:16 PM, Bill Hoffman wrote:

>
> -  On linux spaces in the path do not work, I get this error:
>
> http://www.cdash.org/CDash/**viewBuildError.php?buildid=**2009436
>
>
I think it is a bug in the generator which do not escape the space properly
using the $ character as supported by Ninja.

-- 
Nicolas Desprès
--

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

[cmake-developers] ninja spaces in the path do not work on linux

2012-02-15 Thread Bill Hoffman


-  On linux spaces in the path do not work, I get this error:

http://www.cdash.org/CDash/viewBuildError.php?buildid=2009436


-Bill

--

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