- Mar 30, 2012
-
-
Tobias Hunger authored
Change-Id: I3a480e5dc0bc3b4270057148b6b9a405323ca5ec Reviewed-by:
Daniel Teske <daniel.teske@nokia.com>
-
- Feb 24, 2012
-
-
Tobias Hunger authored
Really ugly hack to get remote deployment for desktop linux going again. This is a regression that we recently introduced and should have again in the next version of Qt Creator. The proper fix will be happening when adding a system environment for Qt Creator 2.6. Change-Id: Iaa9782eda0f7bb434ac5a538a4ef49be11eb3643 Reviewed-by:
Christian Kandeler <christian.kandeler@nokia.com>
-
- Feb 23, 2012
-
-
Thomas Hartmann authored
We support (pure) qml projects only on the desktop. Change-Id: Ib68d8ddab053a2b4e4b60cc07e9408eff0e27d63 Reviewed-by:
Alessandro Portale <alessandro.portale@nokia.com> Reviewed-by:
Christian Kandeler <christian.kandeler@nokia.com>
-
- Feb 15, 2012
-
-
Erik Verbruggen authored
Getting the #include directives ready for Qt5. This includes the new-project wizards. Change-Id: Ia9261f1e8faec06b9285b694d2b7e9a095978d2b Reviewed-by:
Eike Ziller <eike.ziller@nokia.com>
-
- Feb 09, 2012
-
-
Alessandro Portale authored
Symbian and Meego components are only supported on the devices and for the simulator. Change-Id: I21db10d32a80eac9ea04b678efd0e7dd65bccaff Reviewed-by:
Thomas Hartmann <Thomas.Hartmann@nokia.com>
-
- Feb 08, 2012
-
-
Thomas Hartmann authored
This patch introduces platforms as a top level topic when choosing a wizard. Also I changed the categories and priorities. Details: 1. I did change the way the dialog/view is structured in newdialog.cpp 2. I added platformName() and supportsPlatform() to BaseQtVersion. I needed two functions because the Simulator does not provide a platform and therefore has no platformName but supports two platforms. I still have to turn the platform names into proper constants. 3. I changed the categories and priorities to get the layout that was discussed. (I had to touch quite alot of files but this is mostly trivial) 4. I added a combobox that allows filtering for platforms. 5. I added flags() to IWizard to indicate that a wizard is platform independent. Change-Id: I86c7ad628a431ad06505c76580885c6e6c3ddc23 Reviewed-by:
Alessandro Portale <alessandro.portale@nokia.com>
-
- Jan 26, 2012
-
-
hjk authored
Change-Id: I2b72b34c0cfeafc8bdbaf49b83ff723544f2b6e2 Reviewed-by:
Daniel Teske <daniel.teske@nokia.com>
-
- Jan 18, 2012
-
-
Thomas Hartmann authored
Every wizard now implements requiredFeatures() to define a feature set. If the feature set is not satisfied by the available Qt Versions, the wizard is not shown in the create file/project dialog. Every Qt version can define the provided feature set in availableFeatures() defined in BaseQtVersion. Change-Id: Ie9e2c210d19187b2296451948c36d274f2096623 Reviewed-by:
Daniel Teske <daniel.teske@nokia.com> Reviewed-by:
Alessandro Portale <alessandro.portale@nokia.com>
-
- Jan 14, 2012
-
-
Friedemann Kleint authored
Change-Id: If9fd111032975d2a313084f5fedf20561806e268 Reviewed-by:
Daniel Teske <daniel.teske@nokia.com>
-
- Dec 07, 2011
-
-
Daniel Teske authored
Change-Id: I3afc3a4f2e0dd2671279c2d071779f1d7b277849 Reviewed-by:
Tobias Hunger <tobias.hunger@nokia.com>
-
- Nov 03, 2011
-
-
hjk authored
Change-Id: If18afb5d4665924e7d9250dccbc60a65e6daa75e Reviewed-by:
Eike Ziller <eike.ziller@nokia.com>
-
- Sep 08, 2011
-
-
Tobias Hunger authored
* Set a null-ABI for toolchains where detection of ABI failed: This allows the user to select any tool chain. * Warn if ABI detection fails by showing a message in the Qt version setup dialog * Do not override the mkspec if the Qt version has a null ABI only: We (have to) trust the user to know what he is doing in that case. * GCC: Add version information to GCC tool chain and use it to select the mkspec on Mac. * GCC: Do not override mkspec if we do a cross-compile (and actually detect that). * GCC: Leave out -32 or -64 from mkspec if the compiler binaries ABI matches the target ABI. * Linux-generic is compatible with all other linuxes (both ways) The targets themselves do additional filtering and will remove anything that does not work for them anyway. Task-number: QTCREATORBUG-5756 Task-number: QTCREATORBUG-5960 Change-Id: Ib3c0ac91f3aa8e2a823e3e9891a02bdccb97af14 Reviewed-on: http://codereview.qt-project.org/4281 Reviewed-by:
Qt Sanity Bot <qt_sanity_bot@ovi.com> Reviewed-by:
Daniel Teske <daniel.teske@nokia.com>
-
- Jul 20, 2011
-
-
Daniel Teske authored
Change-Id: Ie6275ebf6a49f0b1732cc146abeaa23c7b6eafd4 Reviewed-on: http://codereview.qt.nokia.com/1843 Reviewed-by:
Qt Sanity Bot <qt_sanity_bot@ovi.com> Reviewed-by:
Kai Koehne <kai.koehne@nokia.com>
-
- May 24, 2011
-
-
dt authored
Also adjust qmldumptool to remove the dependency on qt4project/qmlproject, by passing in the qtversion instead of figuring it out in qmldumptool. Change-Id: Ie6ac582d36bfef290313c0716b33b62fcf42630c Reviewed-on: http://codereview.qt.nokia.com/70 Reviewed-by:
Qt Sanity Bot <qt_sanity_bot@ovi.com> Reviewed-by:
Daniel Teske <daniel.teske@nokia.com>
-
- May 16, 2011
-
-
dt authored
Actually pass on the base qt version value... Also fix a small issue on the qt versions page that prevented the invalid reason showing up for a nameless version Task-Nr: QTCREATORBUG-4899
-
- May 13, 2011
-
-
Tobias Hunger authored
We can figure out now whether something was build with mingw or not.
-
- May 12, 2011
-
-
dt authored
Split up target specific code into subclasses. Also change Qt4BuildConfiguration to allow a null qtversion. Remove code that relied on always having a qt version. Also make it possible to remove all qt versions. Completly change the qt in path autodetection to be only a fall back if no configuration was found. Note: For now the old settings are not removed, as such 2.2 and master can coexist. Reviewed-By: hunger
-