| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
The UWP support in Qt was removed with Qt 6 and the support in Qt
Creator is basically untested.
Change-Id: I3148efdb596ddd326f590c14c22cc77ded2582a7
Reviewed-by: <[email protected]>
Reviewed-by: Eike Ziller <[email protected]>
|
| |
|
|
|
| |
Change-Id: Ie0ad653d7611a2db8421baed68a7dbb9d89e06a7
Reviewed-by: Christian Stenger <[email protected]>
|
| |
|
|
|
|
|
|
|
| |
The "Smuggle in the button" hack broke and made Creator crash when a run
configuration is opened. Having a "proper" aspect for the arguments
saves the day.
Change-Id: I45646318f5e8c42fb1ed64c07de5728d9d08c431
Reviewed-by: hjk <[email protected]>
|
| |
|
|
|
|
|
|
| |
Allows to use constants in fewer places, similar to what e.g.
RunConfiguration does.
Change-Id: I9d049128206c4acf0ce14b06b66d6c090a7c5242
Reviewed-by: Christian Kandeler <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <[email protected]>
|
| |
|
|
|
|
|
|
| |
The extra parameter was always computed but used only in one place,
and that use got removed lately.
Change-Id: Ie10c0107ca70ee97ce03f83294992aab8d1a3ffe
Reviewed-by: Christian Kandeler <[email protected]>
|
| |
|
|
|
|
|
| |
Less code.
Change-Id: If168fe0a2ff6b60bbac638689d8979d9c630bfad
Reviewed-by: Oliver Wolff <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This follow the rough pattern of recent *RunConfigurationFactory changes
for build and deploy configurations.
- Collapse the two lines of constructors similar to what
890c1906e6fb2ec did for RunConfigurations
* Deploy* was purely mechanical
* Build* ctors are split in connects() in the ctor body
to create "empty shell for clone" etc
and build step additions in initialize() functions which
are only used in the create() case.
-- Allows to collapse the shared 'ctor()' functions, too.
- Move FooBuildConfigurationFactory::create() implementations
to FooBuildConfiguration() constructor. That was a strange
and unneeded ping-pong between factories and objects, and
furthermore allows one level less of indirection (and for a
later, left out here, some reduction of the
FooBuildConfiguration interfaces that were only used to
accommodate the *Factory::create() functions.
- Most {Build,Deploy}Configuration{,Factory} classes had a canHandle(),
but there wasn't one in the base classses. Have one there.
- Most canHandle() functions were checking simple restrictions on
e.g. project or target types, specify those by setters in the
constructors instead and check them in the base canHandle()
- clone() is generally replaced by a creation of a "shell object"
and a fromMap(source->toMap()), implemented in the base, there
are two cases left for Android and Qbs that needed(?) some extra
polish
- generally use canHandle() in base implementation, instead
of doing that in all Derived::canFoo()
- as a result, canCreate/create/canClone/clone reimplementations
are not needed anymore, keep the base implementation for
now (could be inlined into their only users later), but
de-virtualize them.
- Combine Ios{Preset,DSym}BuildStepFactory. There was only one
'dsym' build step they could create.
- Split the 'mangled' id into the ProjectConfiguration subtype
specific constant identifier, and a QString extraId() bit.
Only maintain the mangled id in saved settings.
- Make ProjectConfiguration::m_id a constant member, adapt
all constructors of derived classe.
Not done in this patch:
- Finish possible cosmetic changes on top
- Add a way to specify restrictions to supported Qt versions
(used in Android/Ios), as the base implementation does not
depend on the qtsupport plugin
- Combine the QList<X> availableFoo() + createFoo(X) function
pairs to somthing like a direct
QList<struct { X; std::function<X()>; }> fooCreators()
to avoid e.g. the baseId.withSuffix() <-> id.suffixAfter(base)
pingpong
- Remove the *Factories from the global object pool
- Do something about priority(). Falling back to plain
qmake in android+qmake setup is not helpful.
Change-Id: I2be7d88d554c5aa8b7db8edf5b93278e1ae0112a
Reviewed-by: Tobias Hunger <[email protected]>
|
| |
|
|
|
|
|
| |
Kudos to cgmb and https://github.com/cgmb/guardonce
Change-Id: Ifa8970734b8d43fd08c9260c645bdb0228633791
Reviewed-by: Tobias Hunger <[email protected]>
|
| |
|
|
|
|
|
| |
* Update files in src/plugins
Change-Id: Ia5d77fad7d19d4bb3498e78661982f68729adb22
Reviewed-by: Tobias Hunger <[email protected]>
|
| |
|
|
|
|
|
|
| |
This information can be used to get information from earlier steps,
which e.g. queried for android devices to deploy to.
Change-Id: Iefe1c9443915cb6211f86f98ff7aaf3cb75145ba
Reviewed-by: Niels Weber <[email protected]>
|
| |
|
|
|
|
| |
Change-Id: I2aa3a32a0d30f1d122977d94d4109227dea6bbd7
Reviewed-by: Niels Weber <[email protected]>
Reviewed-by: Tobias Hunger <[email protected]>
|
| |
|
|
|
| |
Change-Id: I711d5fb475ef814a1dc9d2822740e827f3f67125
Reviewed-by: Alessandro Portale <[email protected]>
|
| |
|
|
|
|
|
| |
Task-number: QTCREATORBUG-13275
Change-Id: I1fb8b951468793bd6edc0e10e53d708a876c0bf3
Reviewed-by: Andrew Knight <[email protected]>
Reviewed-by: Joerg Bornemann <[email protected]>
|
| |
|
|
|
| |
Change-Id: I3c22ef2685d7aa589f5d0ab74d693653a4c32082
Reviewed-by: Alessandro Portale <[email protected]>
|
| |
|
|
|
| |
Change-Id: I231b232861e78bb718134ef2e3494c10216576ae
Reviewed-by: Oliver Wolff <[email protected]>
|
| |
|
|
|
|
|
|
|
| |
Add device detection for WP8.1, and use the Appx packaging codepath
for these devices. Rely on winrtrunner to automatically select the
correct profile.
Change-Id: Ibd1d415644fdc8fd007969be25213410c3c0e0a7
Reviewed-by: Oliver Wolff <[email protected]>
|
| |
|
|
|
|
| |
Change-Id: I4c61e1b19c89277829148d31f8ff2b971375d93e
Reviewed-by: Andrew Knight <[email protected]>
Reviewed-by: Joerg Bornemann <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
| |
A simple line edit to display or change the arguments that are
passed to windeployqt.
Task-number: QTCREATORBUG-11693
Change-Id: I059f5c2af3fce17f9f8463ecfa2af91f21ffe6d8
Reviewed-by: Oliver Wolff <[email protected]>
Reviewed-by: Andrew Knight <[email protected]>
|
|
|
Done-with: Andrew Knight <[email protected]>
Done-with: Friedemann Kleint <[email protected]>
Change-Id: I4772938e775056d6a36a7e75f868921a74007862
Reviewed-by: Christian Kandeler <[email protected]>
Reviewed-by: Eike Ziller <[email protected]>
|
