QtCreator 4.0.1 has several issues

zd3nik

Anyone else experiencing these issues in QtCreator 4.0.1? Anyone know if there's a solution for any of them?

Many compile errors are not captured in the "issues" list. I now have to wade through the compiler output pane to find errors and the source file plus line number.
There is a long pause every time I save. I'm not working on huge projects so it's not because the files are really large or there's a lot of files. My drives are SSD so it's not slow drives. My system is completely idle and has gigabytes of free RAM so it's not caused by other tasks bogging the system down. This is entirely new and started when I updated to qtcreator 4.
Build now uses "cmake --build" instead of "make". Is there a way to make "cmake --build" use multiple cores, like "make -j4"?

I must say, it's pretty disappointing that this latest version would have such flaws in such basic and fundamental features. How did these issues make it into a release version? Very disappointing indeed.

kshegunov

@zd3nik said:

Anyone else experiencing these issues in QtCreator 4.0.1?

I'm using Qt Creator 4.0.0 and I don't experience neither issue #1 nor #2. I don't use cmake so I have no clue whether or not issue #3 is present.

I must say, it's pretty disappointing that this latest version would have such flaws in such basic and fundamental features.

It should be established first that said flaws are in those basic and fundamental features and don't lie somewhere else.

How did these issues make it into a release version?

Provided your issues can be reproduced (which I couldn't) then you should ask the Qt Creator developers that.

Kind regards.

zd3nik

@kshegunov Thanks for the feedback, but don't brush off the issues I'm seeing simply because you aren't experiencing them. You are on 4.0.0, I am on 4.0.1. I am using cmake, you are not. I'm on Centos 7 (clean OS install just before installing Qt), I'm willing to bet you are on a different platform. And #1 doesn't happen on every compile error so you may have simply been lucky, or I've been unlucky. I haven't narrowed down whether #1 is only happening on a certain class of errors or not. The 2 times it's happened (out of about the 5 total compile errors I've encountered since updating) one was due to a missing "#include <stdexcept>", the other was a template error (if I remember correctly).

I've been using qt + qtcreator for years. And this is the first version they've released with these kinds of issues. There have been other issues in other versions of course, but none so glaringly inconvenient for basic every day development. Which is why I'm so baffled that they made it into a release.

kshegunov

@zd3nik

Thanks for the feedback, but don't brush off the issues I'm seeing simply because you aren't experiencing them.

I don't. I simply pointed out I could not reliably establish fault with Qt Creator.

I'm on Centos 7 (clean OS install just before installing Qt), I'm willing to bet you are on a different platform.

Debian stretch (it's a rolling release, but currently I'm running the 4.5.x kernel).

And #1 doesn't happen on every compile error so you may have simply been lucky, or I've been unlucky.

It is certainly possible. If you're able to pinpoint the exact errors triggering the behavior, I'd be willing to try it on my machine.

Which is why I'm so baffled that they made it into a release.

Well, it's a major version, so some uncaught bugs are bound to happen until the release is polished. Still, you're better directing such questions at the developers (e.g. on the mailing list).

Kind regards.

JohanSolo

@zd3nik said:

Build now uses "cmake --build" instead of "make". Is there a way to make "cmake --build" use multiple cores, like "make -j4"?

You can do it like this: cmake --build -- -j4

zd3nik

@JohanSolo Excellent. Thanks! That's one down.

zd3nik

Turns out it's pretty easy to reproduce #1:

File 1: testing/CMakeLists.txt

project(testing)
cmake_minimum_required(VERSION 2.8)
add_executable(testing "src/TestClass.cpp")

File 2: testing/src/TestClass.cpp

int main(const int, const char*[]) {
  std::cerr << "testing" << std::endl;
  return 0;
}

Open that CMakeFiles.txt with qtcreator 4.0.1, let it create default build configuration(s), and the hit build. There will be errors in the "Compile Output" tab, but nothing in the "Issues" tab.

Compile Output tab:

00:21:07: Running steps for project testing...
00:21:07: Starting: "/usr/bin/cmake" --build . --target all
[100%] Building CXX object CMakeFiles/testing.dir/src/TestClass.cpp.o
testing/src/TestClass.cpp: In function 'int main(int, const char**)':
testing/src/TestClass.cpp:2:3: error: 'cerr' is not a member of 'std'
   std::cerr << "testing" << std::endl;
   ^
testing/src/TestClass.cpp:2:29: error: 'endl' is not a member of 'std'
   std::cerr << "testing" << std::endl;
                             ^
gmake[2]: *** [CMakeFiles/testing.dir/src/TestClass.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/testing.dir/all] Error 2
gmake: *** [all] Error 2
00:21:07: The process "/usr/bin/cmake" exited with code 2.
Error while building/deploying project testing (kit: Desktop)
When executing step "Make"
00:21:07: Elapsed time: 00:00.

QtCreator info:

Qt Creator 4.0.1
Based on Qt 5.6.1 (GCC 4.9.1 20140922 (Red Hat 4.9.1-10), 64 bit)

Built on Jun 6 2016 17:13:49

From revision 6863acfe91

other info:

cmake version 2.8.11
g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
Linux 3.10.0-327.18.2.el7.x86_64 #1 SMP Thu May 12 11:03:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

tekojo

@zd3nik sounds like you should open a bug on bugreports.qt.io on the QtCreator project. The post has pretty much all the information a good bugreport needs.
On bugreports you'll get the Creator developers to look at the issue.

zd3nik

Also turns out the issue is their switch to "cmake --build" instead of "make". I just changed the project build step to run "make" as a custom process step and deleted the default cmake --build step. After doing that compile errors from the above example show up into "Issues" tab.

Switching to make instead of cmake --build has also solved the long delay while saving problem.

kshegunov

@zd3nik
Then, after that last piece of information, I'm with @tekojo - file a bug report.

Kind regards.

zd3nik

Looks like someone has already filed a bug about the issues pane not getting populated: https://bugreports.qt.io/browse/QTCREATORBUG-15673

I rescind my last comment about the hang problem being solved however. The hang during save went away in the cmake example I gave above (after changing build to use make instead of cmake --build) but I have another project that uses qmake and it is having the 2 second hang on every save issue. One time I pressed several keys while it was hung and that resulted in the IDE completely loosing touch with the keyboard. Only mouse interactions worked after that. I had to restart qtcreator to get it back to paying attention to the keyboard again.

zd3nik

If there's anyone else out there experiencing the hang during save problem, I've filed QTCREATORBUG-16453.

Keyos

I had the multicore compilation slow down problem n.3 when updating to 4.0.0 as well on windows, i fixed it forcing the mingw kit to use jom in the options->build&tun->kits by setting enviroment: MAKE_COMMAND=C:\Qt\Tools\QtCreator\bin\jom.exe
https://forum.qt.io/topic/67482/qtcreator-4-0-0-no-more-mingw-parallel-compilation/9