[prev in list] [next in list] [prev in thread] [next in thread]
List: cmake
Subject: Re: [CMake] spaces in generator strings troublesome (Michael Ellery)
From: Stefan.Waigand () continental-corporation ! com
Date: 2017-11-22 17:38:23
Message-ID: OF6530280D.24AE79E7-ONC12581E0.005E1300-C12581E0.0060E64C () continental-corporation ! com
[Download RAW message or body]
Dies ist eine mehrteilige Nachricht im MIME-Format.
Dies ist eine mehrteilige Nachricht im MIME-Format.
--=_alternative 0060E64BC12581E0_=
Content-Type: text/plain; charset="US-ASCII"
Hi Michael Ellery
thank you for your reply.
> perhaps handle arguments as an array variable in bash - it?s a
> slightly saner way to deal with args with spaces:
>
> CMDLINE=(. -G"Unix Makefiles") && cmake "${CMDLINE[@]}?
Well i already got it working in bash when i wrote that. I have the
parameters in a variable and i use eval to execute:
eval $CMAKE_EXECUTABLE $CMAKE_PARAMS_ALL
My point is not i cannot solve the problem. My point is, i like to
simplify this in the future.
The current solution is not nice - it is a workaround. It is more
difficult to understand and maintain as it needs to be. And i am not the
only one who has to deal with this problem. CMake uses spaces inside
arguments where spaces are usually for separation of arguments. Do you
agree?
Countless hours i spent debugging similar problems with paths like
c:\Program Files. I know, one shouldn't use windows as development
environment, but this is something we cannot change unfortunately.
Since we force our developers to not install their perl, compilers etc. in
such paths, things are much better.
I appreciate having the same in CMake.
Isn't it as simple as replacing all '_' by ' ' to support this and be
backward compatible? Are there other reasons i do not see?
So i again like to kindly ask you to support (besides the established way)
a command line like
cmake . -GUnix_Makefiles
Thank you,
Stefan
--=_alternative 0060E64BC12581E0_=
Content-Type: text/html; charset="US-ASCII"
<tt><font size=2>Hi Michael Ellery</font></tt>
<br>
<br><tt><font size=2>thank you for your reply.</font></tt>
<br><tt><font size=2><br>
> perhaps handle arguments as an array variable in bash - it?s a <br>
> slightly saner way to deal with args with spaces:<br>
> <br>
> CMDLINE=(. -G"Unix Makefiles") && cmake "${CMDLINE[@]}?</font></tt>
<br>
<br><tt><font size=2>Well i already got it working in bash when i wrote
that. I have the parameters in a variable and i use eval to execute:</font></tt>
<br><tt><font size=2> eval $CMAKE_EXECUTABLE $CMAKE_PARAMS_ALL</font></tt>
<br>
<br><tt><font size=2>My point is not i cannot solve the problem. My point
is, i like to simplify this in the future. </font></tt>
<br><tt><font size=2>The current solution is not nice - it is a workaround.
It is more difficult to understand and maintain as it needs to be. And
i am not the only one who has to deal with this problem. CMake uses spaces
inside arguments where spaces are usually for separation of arguments.
Do you agree?</font></tt>
<br>
<br><tt><font size=2>Countless hours i spent debugging similar problems
with paths like c:\Program Files. I know, one shouldn't use windows as
development environment, but this is something we cannot change unfortunately.
</font></tt>
<br><tt><font size=2>Since we force our developers to not install their
perl, compilers etc. in such paths, things are much better.</font></tt>
<br><tt><font size=2>I appreciate having the same in CMake.</font></tt>
<br>
<br><tt><font size=2>Isn't it as simple as replacing all '_' by ' ' to
support this and be backward compatible? Are there other reasons i do not
see?</font></tt>
<br>
<br><tt><font size=2>So i again like to kindly ask you to support (besides
the established way) a command line like</font></tt>
<br><tt><font size=2>cmake . -GUnix_Makefiles</font></tt>
<br>
<br><tt><font size=2>Thank you,</font></tt>
<br><tt><font size=2>Stefan</font></tt>
--=_alternative 0060E64BC12581E0_=--
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at: \
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more information \
on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at \
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic