We are happy to announce the release of Qt Creator 4.11 Beta!
Projects
We added experimental support for Qt for WebAssembly and Qt for MCUs.
We improved the general handling of configuring, building and running projects in so many smaller ways that I fail to choose anything for being highlighted here.
If you use CMake 3.14 or later we now use CMake's file-base API for configuring and parsing projects. Which behaves much more reliably than the previous server-mode, especially if you also use CMake from a terminal or other applications.
Editing
Our client for the Language Server Protocol now supports the protocol extension proposal for semantic highlighting.
Regarding highlighting, we fixed that explicit colors in KSyntaxHighlighting files were completely ignored.
The configuration of a Python language server is much easier now.
We added the option to change the line ending style for opened files via the editor tool bar.
You can edit QML bindings directly in Qt Quick Designer now.
Other
There are so many more things that you'll find in our change log.
Get Qt Creator 4.11 Beta
The opensource version is available on the Qt download page under "Pre-releases", and you find commercially licensed packages on the Qt Account Portal. Qt Creator 4.11 Beta is also available under Preview > Qt Creator 4.11.0-beta1 in the online installer. Please post issues in our bug tracker. You can also find us on IRC on #qt-creator on chat.freenode.net, and on the Qt Creator mailing list.
Thank you, Creator Rulez!
However: The project view looks differently now when CMake 3.14 file is used. I was hoping that we are having now a sane project view and by sane I mean a simple filtered directory which shows all sources and headers and skips garbage. What we have instead is a build dependency view where source files are sorted below target nodes. This may be useful in some cases but the number 1 view of an IDE should be a traditional project view. I know that there is a very useful file system view - I would still prefer a plain boring project view which lists all files reported by CMake in the correct directory.
What about QTCREATORBUG-22888 Clang Code Model/Autocomplete not working with GCC precompiled headers? The bug tracker says it's fixed with version Qt Creator 4.11.0-beta1. But for me on Windows 64bit-version I still see the bug behavior in this Beta. With recently published version
Qt Creator 4.10.1 this bug is gone for me and everything is perfect regarding this issue, but now its coming back in version 4.11.0 beta.
Should be really fixed now. CMake 3.16 is still in beta and it's reporting of pch header file changed from absolute to relative path. Thank you for testing.
> We added experimental support for Qt for WebAssembly
How does this support look like?
The plugin introduces support for emscripten (in form of a Qt Creator toolchain) and for launching applications in a web browser via emrun (Qt Creator runconfiguration). The detection of emscripten is automatic.
Mine didn't get detected on Ubuntu, but I also how wonder how it would have been? I had to checkout emscripten and use its builder, and have to manually use it's script to set the environment variables before being able to use em++.
The plugin parses ~/.emscripten. Do you have that file, and does it have a structure like EMSCRIPTENROOT = 'c:/Users/alportal/dev/emsdk/emscripten/1.38.27'_?
Note: ~/.emscripten is a Python script, and if it more complex than FOO = '/bar' the parsing will fail, and the plugin should rather let Python interpret that file.
I checkout emscripten and install/activate the matching version as described here: https://doc.qt.io/qt-5/wasm...
I didn't have ~/.emscripten - first time I've heard of it. I created it. Also, the webassembly plugin is disabled by default in Qt Creator, I had to turn that on.
Though nothing was still detected after this.
Running emsdk activate latest gives this - it's putting the file into the same directory, not into ~/.emscripten:
$ ./emsdk activate latest
Writing .emscripten configuration file to user home directory /home/vadi/Programs/emsdk
Looks like it was a bug in emscripten, fixed in recent git:
$ ./emsdk activate latest
Writing .emscripten configuration file to user home directory /home/vadi/
Thank you. Interesting variation, I would expect that when activating with --embedded parameter.
Good to know that it is fixed. I blindly trusted https://emscripten.org/docs...
But I think it would be a good idea to add the possibility for a user-defined path to an emscripten installation. For a case that you had, and for the --embedded case.
Agreed. However, with this enabled, it still doesn't get picked up as a kit. Here's my ~/.emscripten: https://hastebin.com/okubaj...
And this is how my setup looks like. Is anything wrong? I'd expect Webassembly to be an available kit:
https://uploads.disquscdn.c...
Your .emscripten looks good! :) Whether Qt Creator is able to use it can be seen in the Options->Kits->Compilers tab which should contain an Emscripten Compiler entry:
https://uploads.disquscdn.c...
In addition, you need a Qt for WebAssembly version which you can obtain from the online installer/Maintenancetool:
https://uploads.disquscdn.c...
Aha! My emscripten was detected right, but I didn't have WebAssembly in the installer - I built Qt myself a few months ago to get the new threads support. Thanks, I'll download it and try.
Oh no! It decided to print out the webassembly text expression, which took half an hour, and it didn't work in the end: https://hastebin.com/peyeji...
Perhaps we can continue the discussion in the form! I've started a thread on https://forum.qt.io/topic/1...
guys, how to install qt creator offline installer without inet connection?I know it sounds oddly but offline installer requires be online.my host is a behind of proxy . which doesn't allow most of outgoing connections.
and it hangs on license pre-conditions check....
I love the unified source/headers view that's now available in cmake. Thanks!
Nitpicking: "Regarding highlighting, we fixed that explicit colors in KSyntaxHighlighting highlighting files were completely ignored." - a bit too much "highlighting" for my eyes :)
Probably had my sunglasses on. Thanks. Fixed.