[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: CMake Manager and escaping
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2009-02-07 1:00:48
Message-ID: 757d9a550902061700s55ef4a47t5d16796fe9497f23 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I'll check that when I get back home (asap).

On Fri, Feb 6, 2009 at 11:47 PM, Andreas Pakulat <apaku@gmx.de> wrote:

> Hi,
>
> with KDevelop4 on windows some issues seem to be easily found :)
>
> One such issue is escaping (or rather unescaping) in the cmake parser.
> Unfortunately there seems to be some logic missing for that step. For
> example running an external process produces something like this
>
> "C:\foo"
>
> which gets stored in a variable and supposedly later on used by the parser
> after unescaping it to "C:foo" which of course is wrong.
>
> Fixing that one place is no big deal (i.e. s/\\/\\\\/ in the output), but
> it makes me wonder how many other places might need this and wether anybody
> ever checked the CMake sources how and when they do the unescaping of
> variable values.
>
> Andreas
>
> --
> There is a 20% chance of tomorrow.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel@kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>

[Attachment #5 (text/html)]

I&#39;ll check that when I get back home (asap).<br><br><div class="gmail_quote">On \
Fri, Feb 6, 2009 at 11:47 PM, Andreas Pakulat <span dir="ltr">&lt;<a \
href="mailto:apaku@gmx.de">apaku@gmx.de</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> Hi,<br>
<br>
with KDevelop4 on windows some issues seem to be easily found :)<br>
<br>
One such issue is escaping (or rather unescaping) in the cmake parser.<br>
Unfortunately there seems to be some logic missing for that step. For<br>
example running an external process produces something like this<br>
<br>
&quot;C:\foo&quot;<br>
<br>
which gets stored in a variable and supposedly later on used by the parser<br>
after unescaping it to &quot;C:foo&quot; which of course is wrong.<br>
<br>
Fixing that one place is no big deal (i.e. s/\\/\\\\/ in the output), but<br>
it makes me wonder how many other places might need this and wether anybody<br>
ever checked the CMake sources how and when they do the unescaping of<br>
variable values.<br>
<br>
Andreas<br>
<font color="#888888"><br>
--<br>
There is a 20% chance of tomorrow.<br>
<br>
_______________________________________________<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" \
target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
 </font></blockquote></div><br>



_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


[prev in list] [next in list] [prev in thread] [next in thread]