GitLab

This partly addresses QTCREATORBUG-7754: Settings are lost way less
often this way. We do not really want to save whenever settings might
have been touched, so this seems like a good compromise to me.

Most modes at least have some view specific settings that need saving,
so lets just save everything on each mode change. Settings are only
written to disk if they really changed nowadays, so this should be fine.

Task-number: QTCREATORBUG-7754
Change-Id: I26ae18cae38754da6c79a8b870ffae2e681db7c1
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

Until now, the code is duplicated in all deploy steps that
need access to the device, which obviously doesn't scale.
We now do it once in a dedicated step.

Change-Id: I27f67f28a2e9ccaf9d2b3a5a9635d84b14f5eb07
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>

Change-Id: I89904d877d42904b9c37542ad3b51fe513542cfd
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>

Change-Id: I5aa424bacf9f66761d335f5b53734453ee864b80
Reviewed-by: Robert Loehning <robert.loehning@nokia.com>
Reviewed-by: hjk <qthjk@ovi.com>

- Factor out message/tooltips for breakpoints on functions.
- Add stringlist of break functions to CdbOptions.
- Set breakpoints with module, ignore response.

Change-Id: If5cf7647b190057c18d8499b9f4862696610e4f6
Reviewed-by: hjk <qthjk@ovi.com>

Setting Tools/Options/Environment/General/Terminal to one of the
following works now as expected.

  1. xterm -e
  2. aterm -e
  3. rxvt -e
  4. urxvt -e
  5. xfce4-terminal -x
  6. konsole --nofork -e
  7. gnome-terminal -x

Without the '--nofork' option for konsole, from creator's pov, the
terminal emulator will finish immediately and therefore creator closes
the local socket. As a result of this, the user is presented with sth.
like this (from the stub):

    Cannot connect creator comm socket /tmp/qt_temp.A13523/stub-socket:
    No such file or directory.

Task-Number: QTCREATORBUG-1633
Change-Id: I732e20d34aebdc1591355e0c4e78c907f439924c
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

Current display doesn't make sense (to me :))

Active class is the middle one, derived classes should be top-down, but
base classes should be bottom-up. That's easier to understand.

Change-Id: I06693da37c834f5a99fd62ae29a91d958bafe136
Reviewed-by: Leandro Melo <leandro.melo@nokia.com>

Should be called less often now.

Change-Id: Id7cd751e2be348c13ecc7dc02bffd0e33ccc297c
Reviewed-by: Daniel Molkentin <daniel.molkentin@nokia.com>

Previously we detected the duplicates by name and then processed
the missing ones, but this was not handling qualification properly.
Now we process the bases and only after lookup (making sure we
are talking about the *same* types) we add then if necessary.

Change-Id: Ic318b174d2174e24c24a4f2f1b612fbcb3f20491
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>

Change-Id: Ieacef53be501fdddc16c10e9facbb3937cbd37b4
Reviewed-by: Daniel Molkentin <daniel.molkentin@nokia.com>

the parser explicitly excludes complaints about missing files (because
they are pretty common in cumulative mode), so we need to do it ourselves.

Change-Id: I3c36819ab7b26152271e4557b67fb36b0a595b60
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

follow suit with qmake ...

Change-Id: I0221f6c81bc770c37f501d79c31860549c0c0076
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

so they match the Q* counterparts more closely:

ProString: startsWith(), endsWith(), indexOf(), lastIndexOf(),
contains(), at(), length(), QTextStream::operator<<(), toLatin1(),
toInt() & toShort()

ProStringList: length(), removeAt(), contains()

Change-Id: Iab78236f7152f6a4b93709abbf59b9027c44ba2c
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

it's pointless

Change-Id: Ia02762a1f79399970cbdf43b3b20e08b4e54fd3b
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

we can trivially construct a QStringRef from a ProString, so take
advantage of that.

Change-Id: I9aaa1f6d910590872b250a145f16e90984beeb94
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

otherwise it's impossible to migrate the qmake generators to this.

Change-Id: I70c848da2ce428706b960c3c1434c26f7e3a9447
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

the value map stack always has at least one map on it.

Change-Id: I836de07a14754b995403065443d3758bfc6a8683
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

Change-Id: I43eb4a7a94b6df3d964b7bfd1747f953f436ba10
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

QString::replace(QRegExp) pretty much always detaches, so the equality
check was bogus.

Change-Id: Iee9043c1ee3083edaf289886ac11b3e3a501d623
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

we need to interpret the -1 as unsigned for it to mean "unlimited".

Change-Id: I130b809749fa1679a5b2444286baf48cc095c7bf
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

we use the actual current directory as the base dir, as that's closest
to what qmake would do so far. it's completely arbitrary what will
happen when shadow-building or specifying an output directory, and in
creator context it's pretty much meaningless.

Change-Id: I8c490c86fa2606fcee5d176c90c5a84a4783e87b
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

there is actually a qmake test for that.

don't copy anything which is related to loading a qmakespec to the new
evaluator, though - either it will actually load a spec (include(,into))
anyway, or it has a clean slate ($$fromfile() and infile()) and anything
spec-related would be pointless.

Change-Id: I291201a2bf823e863b3ec94be91762954612417d
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

i broke this by switching to using a separate evaluator. the new
evaluator has an empty file stack, so the check would be pointless.
fix it by recoding and traversing the call chain.

Change-Id: Icb1f19adc6e66a865cd5be78eeb1c10072b4f8fc
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

Change-Id: Ib56082091a1f7e3062ff48e981bb4ee8e2dd9357
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

Set debian packaging up when adding a target requiring it are added.

Task-number: QTCREATORBUG-7627
Change-Id: I2e88131f486f6792f38474ed5809dfa5ac7bf0e0
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>

Change-Id: I5235df0110454d246b44e7d6e05b667be4fdb0bc
Reviewed-by: Christian Kandeler <christian.kandeler@nokia.com>

Change-Id: I9df9f158382f4ab7152130d7fb0ef9be311f12bd
Reviewed-by: Christian Kandeler <christian.kandeler@nokia.com>

Seems to be new use in mingw 4.6.

Change-Id: I7331e3be3c14fed86d4eebf333ab4b01d1b237bf
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>

Change-Id: I5f59eed83ac45a2d90c079101158e7e306fd9a3e
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>

Change-Id: Ide5445e1cf488c29be620287759147251bc7c26a
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ifbbd2b7af06eec620a765614792547fff6303f06
Reviewed-by: hjk <qthjk@ovi.com>

CPlusPlus::{Literal,Identifier,IntegerType,NamedType,TemplateNameId}

Change-Id: I1c71be1e284c69c09d8257696feda2974f083c33
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I9b0d56b6f615f567391349404250d05b5c0b9113
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I2b2edbad5b59fdad8a537c82d675cdc8b59eaa82
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>

Task-number: QTCREATORBUG-7721

Change-Id: Ib444d233d99a5121129671debab18557135559f4
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>

Change-Id: I6f060880db7b9360b3d9c548f42cee46468eb4ab
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

Change-Id: Ie7b86009f47b2bb3ae300d1496b3c22cce58f03d
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I6c033c047d134a953291747f2cf044dcaab1d858
Reviewed-by: hjk <qthjk@ovi.com>

The options page deleted the widget, which it does not own.

Remove the deletion, rename GdbOptionsPagePrivate to
GdbOptionsPageWidget and use a QPointer in the GdbOptionsPage,
rename the member to m_widget for clarity.

Change-Id: I211a7cf4d59015c540335bd6313eaff13f1999a4
Reviewed-by: hjk <qthjk@ovi.com>

Fix warning: "Unable to completely determine the host ABI
(x86-windows-unknown-pe-32bit).". It seems mingw32 is no longer
defined in MinGW 4.6; use the more reliable Q_CC_MINGW.

Change-Id: I2d4f84a62b2fe829b3a8d755a76429b94c0109f5
Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com>