Hi,
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.
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.
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?
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
seem to matter since it works in my Win XP installation.
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?
Best regards,
Juha
On 21.05.2014 19:03, Iosif Hamlatzis wrote:
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.
https://www.dropbox.com/s/t9djgevjufj5ekx/only_errors.PNG
https://www.dropbox.com/s/prf0b61pzgwgyw3/warnings_errors.PNG
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.
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.
On 21 May 2014 12:25, Juha Kallioinen <juha.kallioi...@jolla.com
<mailto:juha.kallioi...@jolla.com>> wrote:
On 21.05.2014 09 <tel:21.05.2014%2009>:04, Iosif Hamlatzis wrote:
As I haven't gotten a response I am coming back to the issue:
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.
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.
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.
Is anyone else having the same problem as Iosif?
[1] http://i.imgur.com/MUjDAuM.png
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.
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?
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.
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?
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.
I'm not sure how exactly Qt Creator figures out which binary to
run in a more complex case.
Under the folder
.....\SailfishAlpha4\mer-sdk-tools\MerSDK\SailfishOS-arm7hl are
only files for compiling, packaging and deploying. NO debugging.
eg:
deploy.cmd
gcc.cmd
make.cmd
qmake.cmd
rpm.cmd
rpmbuild.cmd
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.
Best regards,
Juha
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to
devel-unsubscr...@lists.sailfishos.org
<mailto:devel-unsubscr...@lists.sailfishos.org>
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
