src/tools/tools.qbs

import qbs

Project {
    name: "Tools"
    references: [
        "buildoutputparser/buildoutputparser.qbs",
        "qtcdebugger/qtcdebugger.qbs",
        "qtcreatorcrashhandler/qtcreatorcrashhandler.qbs",
        "qtpromaker/qtpromaker.qbs",
        "sdktool/sdktool.qbs",
        "valgrindfake/valgrindfake.qbs",
        "3rdparty/iossim/iossim.qbs",
        "iostool/iostool.qbs"
    ].concat(project.additionalTools)
}
Refactor qbs project files. - Use sub-projects. - Move the main application and the application header products into dedicated files. As a result, qtcreator.qbs becomes much simpler to understand, consisting now of just a bunch of global properties and a few sub-project references. Change-Id: Ic7300d489d3982394be5ad1d12a79a2914320298 Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com> 2013-06-21 13:12:30 +02:00			`import qbs`

			`Project {`
			`name: "Tools"`
			`references: [`
Introduce command-line tool for parsing build output. It makes the functionality of Qt Creator's build-related output parsers available on the command-line. Concrete use case: Run this on the build machines and put the output in the emails sent to potential build breakers. Change-Id: Iea6870ed976790854aecfe3cdc0d5b2296b6bced Reviewed-by: Tobias Hunger <tobias.hunger@digia.com> 2013-10-17 18:47:44 +02:00			`"buildoutputparser/buildoutputparser.qbs",`
Refactor qbs project files. - Use sub-projects. - Move the main application and the application header products into dedicated files. As a result, qtcreator.qbs becomes much simpler to understand, consisting now of just a bunch of global properties and a few sub-project references. Change-Id: Ic7300d489d3982394be5ad1d12a79a2914320298 Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com> 2013-06-21 13:12:30 +02:00			`"qtcdebugger/qtcdebugger.qbs",`
			`"qtcreatorcrashhandler/qtcreatorcrashhandler.qbs",`
			`"qtpromaker/qtpromaker.qbs",`
Add qbs project file for valgrind-fake. Change-Id: I14d1b0e04650ef9c717be3f5ca2d7eab1017cd77 Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com> 2013-09-05 15:08:50 +02:00			`"sdktool/sdktool.qbs",`
ios: preliminary support for ios first work in progress support for ios * separate iosTool using xml communication used for device info and run * iossim tool to handle the simulator * debug prepared but not working * separate gcc toolchain detection fix for simulator 1) add a QT built for ios 2) open a project, for example qtbase/examples/widgets/animation/animatedtiles/animatedtiles.pro 3) build/run... Change-Id: I7e01604e416338cbe4692dfb34f5d3f31312702d Reviewed-by: Eike Ziller <eike.ziller@digia.com> 2013-04-25 16:02:17 +02:00			`"valgrindfake/valgrindfake.qbs",`
			`"3rdparty/iossim/iossim.qbs",`
			`"iostool/iostool.qbs"`
qbs project: Add properties for pulling in additional resources. We need this to build plugins located outside the source tree. Change-Id: Ie587b5e838bf0ce67b19d3222bbc40b53b888e69 Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com> 2013-10-01 10:33:41 +02:00			`].concat(project.additionalTools)`
Refactor qbs project files. - Use sub-projects. - Move the main application and the application header products into dedicated files. As a result, qtcreator.qbs becomes much simpler to understand, consisting now of just a bunch of global properties and a few sub-project references. Change-Id: Ic7300d489d3982394be5ad1d12a79a2914320298 Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com> 2013-06-21 13:12:30 +02:00			`}`