#9432 closed enhancement (fixed)
qt5 5.9.1
| Reported by: | Pierre Labastie | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 8.1 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
new point version. From https://blog.qt.io/blog/2017/06/30/qt-5-9-1-released/:
I am pleased to announce that Qt 5.9.1 is released today. It contains all the latest bug fixes and improvements from Qt 5.9 branch.
Qt Creator 4.3.1 is included in the Qt 5.9.1 offline installer packages and available via the online installer.
As a patch release Qt 5.9.1 does not add any new functionality, just bug fixes and other improvements. For details of the changes compared to Qt 5.9.0 release, please check the Change files of Qt 5.9.1.
Our intention is to make more frequent patch releases for Qt 5.9 LTS than before. So if your most desired fix is not included in Qt 5.9.1 there will be more patch releases in the coming months.
If you are using the online installer, Qt 5.9.1 and Qt Creator 4.3.1 can be updated using the maintenance tool. Offline packages are available for commercial users in the Qt Account portal and at the qt.io Download page for open-source users.
For users targeting iOS we have identified an issue which can be fixed with an additional iOS patch. We know this is unfortunate, but the alternative was to delay the entire release for over one month. In light of this we thought it would be better to release 5.9.1 today, with a hot patch for iOS.
Great! we'll have to update Qt5 every month or so
Change History (8)
comment:1 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
follow-up: 3 comment:2 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
follow-up: 4 comment:3 by , 8 years ago
Replying to bdubbs@…:
This was a bit tricky. The configure now picks up database instances automatically and a change in mariadb-10.2.x changes where MYSQL_VERSION_ID is defined. It is only needed in one file and adding an include statement fixes it.
Had you seen the sentence beginning with "If you have MariaDB-10.2.6 installed, fix a build issue with with MySQL compatibility..."? The include statements look pretty much the same. Will try building with the first one, and let you know.
follow-up: 5 comment:4 by , 8 years ago
Replying to pierre.labastie:
Had you seen the sentence beginning with "If you have MariaDB-10.2.6 installed, fix a build issue with with MySQL compatibility..."?
No, I didn't. A grep in my build directory for MariaDB only showed a hit in changes-5.2.1. Where did you find the above?
follow-up: 6 comment:5 by , 8 years ago
Replying to bdubbs@…:
Replying to pierre.labastie:
Had you seen the sentence beginning with "If you have MariaDB-10.2.6 installed, fix a build issue with with MySQL compatibility..."?
No, I didn't. A grep in my build directory for MariaDB only showed a hit in changes-5.2.1. Where did you find the above?
I meant the sentence (and the sed) is in the current trunk book ;-)
comment:6 by , 8 years ago
Replying to pierre.labastie:
Replying to bdubbs@…:
Replying to pierre.labastie:
Had you seen the sentence beginning with "If you have MariaDB-10.2.6 installed, fix a build issue with with MySQL compatibility..."?
No, I didn't. A grep in my build directory for MariaDB only showed a hit in changes-5.2.1. Where did you find the above?
I meant the sentence (and the sed) is in the current trunk book ;-)
I wrote that.
This was a bit tricky. The configure now picks up database instances automatically and a change in mariadb-10.2.x changes where MYSQL_VERSION_ID is defined. It is only needed in one file and adding an include statement fixes it.
For qtwebengine, the build uses all available cores. My system has 12 cores, but the decease from the last version using 4 cores was only about 43 to 35 SBU.
Fixed at revision 18908.