<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
I can't reproduce this in Windows XP either. I installer Win XP
Pro SP3 (32 bit) and the warnings and errors show up just fine and
warnings can be filtered away.<br>
<br>
Also I don't get the word "warning:" in front of the warning
messages as you can see in the picture I included in the previous
message.<br>
<br>
Is it possible that something in the project you are compiling is
producing these messages since they seem to be slightly different
from the standard messages? Or have you turned on some extra
options in Qt Creator that aren't on by default?<br>
<br>
What I was trying to say about the compiler was that the Qt
Creator that is shipped in the installer is compiled with MSVC
2010. It's not a compiler that can be used with the SDK. But also
it does not <br>
seem to matter since it works in my Win XP installation.<br>
<br>
One more thing for you to check: if you create some other project,
like the default template project and add some code lines that
produce warnings there, do you see the same behavior?<br>
<br>
Best regards,<br>
Juha<br>
<br>
On 21.05.2014 19:03, Iosif Hamlatzis wrote:<br>
</div>
<blockquote
cite="mid:CAD2f6zW4e1idf7R-bxkxJrZpejy57Ms9uVu64RMgVjyHcRrLhA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">As I see you're using a different OS, you use Win7
and I'm on WinXP Pro with SP3, it's one difference. Also you
mention of MSVC2010 for the compiler. I am using the one
provided with the SDK, that's a second difference.
<div>
<br>
</div>
<div><br>
<div class="gmail_extra"><a moz-do-not-send="true"
href="https://www.dropbox.com/s/t9djgevjufj5ekx/only_errors.PNG">https://www.dropbox.com/s/t9djgevjufj5ekx/only_errors.PNG</a></div>
<div class="gmail_extra"><a moz-do-not-send="true"
href="https://www.dropbox.com/s/prf0b61pzgwgyw3/warnings_errors.PNG">https://www.dropbox.com/s/prf0b61pzgwgyw3/warnings_errors.PNG</a></div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">From the two screen captures you can
see that the same icon is used for both warnings and errors.
In the first screen capture I have selected to display only
errors, but you can see warnings as well. In the second
screen capture I have selected to display both warnings and
errors. The result is exactly the same, everything is shown.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">And in both cases you'll see that no
icon is displayed on the line with the error. I know the
usage of #error is not exactly the same as having an actual
compile error, but it was the fastest way to reproduce the
problem.<br>
<br>
<br>
<br>
<div class="gmail_quote">On 21 May 2014 12:25, Juha
Kallioinen <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:juha.kallioinen@jolla.com"
target="_blank">juha.kallioinen@jolla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div class="">
<div>On <a moz-do-not-send="true"
href="tel:21.05.2014%2009" value="+12105201409"
target="_blank">21.05.2014 09</a>:04, Iosif
Hamlatzis wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">As I haven't gotten a response I am
coming back to the issue:
<div><br>
</div>
<div>After updating to the latest SDK on a
Windows XP Pro with SP3 all warnings and
errors have the same icon a red triangle.
Pressing the button on the QtCreator IDE to
display all or only errors doesn't work. Also
double clicking on an error or warning it
doesn't take me to the corresponding
file/line.</div>
</div>
</blockquote>
<br>
</div>
Sorry, I think I did respond in the most annoying way:
"works for me". I don't know what else can be done
since the same Qt Creator source is used to build the
Windows version. The Windows version is built in
Windows 7 (32bit) with MSVC2010 compiler.<br>
<br>
I also tested it in Windows 7 and I do get separate
indication for warnings and errors as you can see [1].
Double clicking on an error/warning does take me to
the corresponding file and line.<br>
<br>
Is anyone else having the same problem as Iosif?<br>
<br>
[1] <a moz-do-not-send="true"
href="http://i.imgur.com/MUjDAuM.png"
target="_blank">http://i.imgur.com/MUjDAuM.png</a>
<div class=""><br>
<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>I have tried this on two different machines
both as an upgrade from previous SDK version
and as a clean installation. All occasions
similar conclusion.</div>
<div><br>
</div>
<div>Another thing is that when I try to debug
on the actual device the application builds
correctly and is automatically deployed on the
device then a pop-up dialogue appears asking
me for an executable, but which .exe or .cmd
file should I use and what parameter should I
pass? I presume as a parameter I should pass
the name of the application I want to debug,
but what is the executable?</div>
</div>
</blockquote>
<br>
</div>
The debugging from Qt Creator works if Qt Creator
knows what the executable it needs to run is. The
pop-up dialogue is an indication that in your project
this is not the case.<br>
<br>
Does the simple Sailfish template project application
work for you in the way that Qt Creator would know
which binary to run and consequently debug?<br>
<br>
The template project is very simple and it is of
template type "app" (which is the default and not
mentioned in the template's .pro file). It only builds
one binary and it's quite obvious for Qt Creator that
that is the binary it needs to run.<br>
<br>
I'm not sure how exactly Qt Creator figures out which
binary to run in a more complex case.
<div class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>Under the folder
.....\SailfishAlpha4\mer-sdk-tools\MerSDK\SailfishOS-arm7hl
are only files for compiling, packaging and
deploying. NO debugging.</div>
<div><br>
</div>
<div>eg:</div>
<div>deploy.cmd</div>
<div>gcc.cmd</div>
<div>make.cmd</div>
<div>qmake.cmd</div>
<div>rpm.cmd</div>
<div>rpmbuild.cmd<br>
</div>
</div>
<br>
</blockquote>
</div>
These files are internal for Qt Creator and SDK use
and there should not be need to study them. Debugging
is not done via any of those scripts as you have
already discovered.<br>
<br>
Best regards,<br>
Juha<br>
<br>
</div>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to <a
moz-do-not-send="true"
href="mailto:devel-unsubscribe@lists.sailfishos.org">devel-unsubscribe@lists.sailfishos.org</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to <a class="moz-txt-link-abbreviated" href="mailto:devel-unsubscribe@lists.sailfishos.org">devel-unsubscribe@lists.sailfishos.org</a></pre>
</blockquote>
<br>
</body>
</html>