- on Windows the export is required, while on Unix everything
gets exported by default.
- for Qt5 based Qt Creator we need the specification of the
json file.
Change-Id: I1e8055fcb2b81d42369f906e1ba42a4c2b811553
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
As the standard Qt Quick wizards can handle BlackBerry
file paths for the QML files, and the
BlackBerryDeployConfiguration automatically sets up a
bar-descriptor.xml file for the project, we can remove
the BlackBerry specific Qt Quick wizards.
Change-Id: I8866fb92c8b1725fb4d4ba7af6bdaa2e15986eb2
Reviewed-by: Nicolas Arnaud-Cormos <nicolas@kdab.com>
Now all dumper autotests pass on Qt 4 and Qt 5 to get a base line
for testing. The intention is to re-enable the disabled tests,
especially the QObject related ones soon.
Change-Id: I18236c86145f7d1fb1ed347e2079d15af086a129
Reviewed-by: hjk <hjk121@nokiamail.com>
Generate plugin metadata for Qt 5 or plugin export for Qt 4.
Change-Id: I9888ebb22204c96755f82efc0dd2bceb51a19b0c
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
An app with Qt Quick {1,2} Application template is installed under /opt/
and there is no easy way to change the installation path.
This change allows users to set installation path in the main pro file.
Change-Id: I0325c54187f781b1ceaaddfd41e913117fa445e6
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
With this patch the attribute isHighlighted="true" in
the manifest.xml allows highlighting demos and examples.
The highlighted demos and examples appear first in the list
and have a blue highlight.
Task-number: QTCREATORBUG-8459
Change-Id: Ieeb888630235e07b1ae1398c5ccdc3d7e8d15dff
Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
In Qt5 the qtquick modules/qtdeclarative plugins are installed in the qml folder
Change-Id: I023e479df529a5f69fb9898389a2f130da3af59b
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Nicolas Arnaud-Cormos <nicolas@kdab.com>
The macros were removed in
07e3bcdc106ac42703ae0fb88b6cac2d2bfdd072 .
Change-Id: I4a43106ca85dc9ed97f75a4505888cb550305a8d
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
Distinguishes the process that starts the terminal from the stub
process, as on mac to support Terminal.app they are different.
Handle the stub not through the process that starts the terminal,
but through the local socket (on *nix).
Replace the blocking wait(...) in the main thread, with a nonblocking
wait in the signal handler when receiving a SIGCHLD, to leave the
main thread able to handle communication with creator.
This change allows the use of terminal emulator commands
that share a single instance or that fork.
So this is also the real fix for QTCREATORBUG-1633 on linux.
If creator crashes the stub and the debugged program live on.
This was done on purpose, it could be changed if considered better.
Task-number: QTCREATORBUG-6371
Task-number: QTCREATORBUG-1633
Change-Id: I4d4fb3a67b1987f4e46e2c603dcefe8c15152ad2
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
QT_VERSION_STR is being read from Qt's source directory
and may differ from the version of the build being used
See also printVersion() in src/app/main.cpp
Change-Id: Ib740c07136e1549b0cbecc8258889688763b0b36
Reviewed-by: Thomas Hartmann <Thomas.Hartmann@digia.com>
This need a qbs build >= commit 5cdf94de to work properly.
Change-Id: If86aedf9e3f9d01ad1202e03221e49698d517666
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
Include the path to /usr/lib/qt4/imports, to allow e.g. QtMultimediaKit
to be found, as it's installed there
Change-Id: I99815e82b8b25973d4347a0e95e1ecf7402b5d7b
Reviewed-by: Mehdi Fekari <mfekari@rim.com>
Reviewed-by: Nicolas Arnaud-Cormos <nicolas@kdab.com>
The new wizard is template based. This allows easy addition of
custom QML templates and also allows us to add more QML wizards
for e. g. components later.
This template mechanism allows substitution in comment, which
allows us to keep valid QML file as templates.
This reduces the maintance burden significantly.
Change-Id: I7766b037635131da2af5aae518d6fe4597ff8b9f
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
