GitLab

This amends commit a6c17fc5.

Change-Id: I365513a9e11e6c07310799f87a4e299cd110dcf3
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>

It breaks running over PuTTY with VcxSrv.

This reverts commit 36c8227c.

Task-number: QTCREATORBUG-18467
Change-Id: Id93497ee24cdb574d1e4a1ac1b0fb112012a695d
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>

Instead of hardcoding the value of LSMinimumSystemVersion in Info.plist
where we will always forget to update it (and since Qt Creator can be
built with multiple versions of Qt, it will almost certainly be wrong
for one of those versions), automatically determine the value from
QMAKE_MACOSX_DEPLOYMENT_TARGET, which is authoritative.

This should prevent mishaps where users try to run Qt Creator on older
OS versions and receive a crash dialog instead of the friendly "This
app requires a newer version of macOS" message that a properly set
LSMinimumSystemVersion value will induce.

The Qbs build is not affected by this problem, as Qbs automatically
handles the minimum deployment target even when a custom Info.plist is
specified.

The solution chosen in this patch was used instead of QMAKE_SUBSTITUTES
because the Qbs build also uses the Info.plist input file and it would
break the Qbs build if the quotes were to be escaped, since it would
become invalid XML.

Change-Id: I20625a2fae546c6597a567f28864b12917e8ac39
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>

This patch also sets the minimumQbsVersion to 1.7 because that's the version
that is actually documented as being required in the README.

Change-Id: I862daaf5fa34ab2cc5db47581689e08aa34f0910
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

According to the README, the minimum version is 10.8, but the code did
not reflect that reality.

Change-Id: I2bbaeefe614cba5b5fa8413b68202bb75f346d70
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

If the default install settings contain a value for
"Settings/InstallSettings", then that is used as the actual path for the
actual install settings instead.

If the path is relative, it is interpreted as relative to Qt Creator's
applicationDirPath.

Change-Id: I212037112e88c60c94239580841aa1400d96fb73
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Kai Koehne <kai.koehne@qt.io>

The original reason for disabling HighDPI scaling on Linux in
7da2b4a3 was unhinted fonts for non-
scaled scenario: QTBUG-46435. That issue had been fixed long ago:
0f7bc885aa7ae8cc3c448cc751aba4eba8c1c8b8

HighDPI support on Linux should by now be good enough to give it another
try by default.

Change-Id: I5b74f46310254c2916a2f16a7655d9f096453cc3
Reviewed-by: J-P Nurmi <jpnurmi@qt.io>
Reviewed-by: Marco Benelli <marco.benelli@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

When Widget Designer is opened with a QMainWindow based form, the
"native" Unity menu bar vanishes. This is a workaround by disabling the
native menu bar integration on Linux.

Task-number: QTCREATORBUG-17519
Change-Id: I93eb3a590200fb8fff90017d8d6eddda8edaa42e
Reviewed-by: André Hartmann <aha_1980@gmx.de>

Currently it is set by passing defines to qmake, which complicates
package build setups.
Set the display version where the numerical version is defined. This
also makes it available to developer builds. Also switch around the
display version and numerical version in the about dialog, since e.g.
"4.3.0-rc1" is more descriptive than "4.2.83".

Change-Id: I26dda427975acdc6cc169f8d625f57918167cf19
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

Change-Id: Icbbe1ebd0f77e32d45c1c3ea3cada7c4aaa59ab2
Reviewed-by: hjk <hjk@qt.io>

Both wrap the corresponding Qt class, but make sure all temporary files
or directories are created inside a "master temporary directory".

Change-Id: I55461be507c828c965224c02863ea5ed9bbf9498
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>

Derive the relative paths used in code from the paths used by the build
system.

Change-Id: I208ee55d3c1ee76921734f5c1c6c40d3fcb9724c
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Orgad Shaneh <orgads@gmail.com>

Change-Id: I9451a0cd7b15bb6c84147298a4f1fde5d67ddf4d
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

Task-number: QTCREATORBUG-17296
Change-Id: I8527c340e2b5af1e7f0b0d1f62ff03cd30c06ff2
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

...by not passing in IDE_LIBEXEC_PATH.

While at it, fix the call to CrashHandlerSetup.

Change-Id: Ie4018bf58f286c121bb85951546c4fe4d31e9959
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

* Put the binary into the libexec path
* Check for process origin more explicitly
* Allow providing the application name
* Allow disabling the restart action

Change-Id: Ide7132215d7c251ce486daab60ac680de3c9f9a6
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>

Change-Id: I6ac6cbe39ba6552b30dc109a2310bff8c16b84e0
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

I also added the qtc prefix to all logging categories.

Task-number: QTCREATORBUG-16767
Change-Id: I04214dba9912fe6c669f10566582d6009b5d75f0
Reviewed-by: Robert Loehning <robert.loehning@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

We only support Qt 5.6 now.

Change-Id: If94864400545b057623e3af0743c55ea1e84e33b
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

"osx" -> "macos"

Change-Id: Ie25e096b2759cf8f96411560fcca337169d80b08
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

QDir::entryList just returns file names as strings. In order to get the
full absolute paths of the font files, we need QFileInfos instead, which
dir.entryInfoList returns.

Change-Id: Ied0fb74afa4d02723d172f06d998a6916d5b0c9a
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@theqtcompany.com>

Broke with 05b5b616

Change-Id: I60c9c243ad858563e793663bb0ce2ffc960c7868
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>

We add all .ttf fonts found in share/qtcreator/fonts to
QFontDatabase.

Change-Id: I133a5298bd4696b99fa2350758baf8abd8b16fd8
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>

Change-Id: I5a66a5b805b912a8ee752306d6c39759085e98ad
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>

The qtc module gathers properties that used to live in the top-level
project file. This is the first step towards making it possible to build
plugins against an installed Qt Creator ("out of source build").

Change-Id: Ia1514cc9c888e80be01b308e908de48980fcbdb8
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>

Change-Id: I7619495818728f7b7196c5f8447bf446eedef248
Reviewed-by: Eike Ziller <eike.ziller@qt.io>

Change-Id: Ic125eba1ceacf3582fffdadd992a46910f6347cc
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

That also enables text preview in Quick Look. Also adds missing items
for .qdoc and .qdocconf files.

Change-Id: I5c3f62aceba9a5d31478d083a9ea0adb2ffbcac1
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

"About Qt Creator..." icon.
Application icon for Windows.
Application icon and document icons (.pro, .pri) for OSX.

Change-Id: Ic751336a42838a63b9590bc69063491e63f552f8
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Diana de Sousa <diana.desousa@theqtcompany.com>

... by default.

Similar to qmake qtc_runnable.

Apply in app.qbs.

Change-Id: I8d43027f683ef18fc5a2745afe9775eb14075e69
Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>

It can be helpful, is not much effort, and parts did not restrict the
install target to non-OS X already.

Change-Id: I3501f37f089e981cf3f72d9250c9b9161d1565d6
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

Kudos to cgmb and https://github.com/cgmb/guardonce

Change-Id: Ifa8970734b8d43fd08c9260c645bdb0228633791
Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>

Change-Id: Ib7008eddf6c638e04711158dcb3543c3d992d7ee
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>

Change-Id: I00d8f36151c13e9f57dc3c53fcb41c1ce0b1d64d
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>

* Update remaining files in src

Change-Id: I1896f17fcf34f71c3310c87899fb5171b8e4afb1
Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>

Commit 59ac67c0 broke this for non-OS X.

Change-Id: Iac23a3e37bd9964af4ffb79be256f59c0b0fedb9
Reviewed-by: Jake Petroules <jake.petroules@theqtcompany.com>

Task-number: QTCREATORBUG-15260
Change-Id: I60bb8c455e708d377828801377c4fee43e654dcb
Reviewed-by: Erik Verbruggen <erik.verbruggen@theqtcompany.com>
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>

Set Qt::AA_EnableHighDpiScaling introduced in Qt 5.6.

Amend change f4e5210c which apparently
was broken by qtbase:add58edcdbd986e68cdd65a2a935b76d85d5b639.

Change-Id: I0a9337f17b02704e36915f78b1321287e4112378
Reviewed-by: Alessandro Portale <alessandro.portale@theqtcompany.com>

Change-Id: Iaa9a3d7ae713347b028e9414cff6028b957300c7
Reviewed-by: Jake Petroules <jake.petroules@theqtcompany.com>

After b42bd585 there was
no automatic scaling of Qt Creator's UI with Qt 5.6 on non-OSX,
anymore.

This commit re-introduces it for Windows.

As a small bonus, now the environment variable is only set during
QApplication creation and unset afterwards. The run environments
are now not affected, anymore.

Change-Id: If0039df500d28a93c1ca8c2df9960992a010723f
Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>