src/tools/tools.pro

TEMPLATE = subdirs

SUBDIRS = qtpromaker \
     qmlpuppet \
     ../plugins/cpaster/frontend \
     sdktool \
     valgrindfake \
     3rdparty \
     qml2puppet \
     buildoutputparser

win32 {
    SUBDIRS += qtcdebugger \
        wininterrupt \
        winrtdebughelper
}

mac {
    SUBDIRS += iostool
}

QT_BREAKPAD_ROOT_PATH = $$(QT_BREAKPAD_ROOT_PATH)
!isEmpty(QT_BREAKPAD_ROOT_PATH) {
    SUBDIRS += qtcrashhandler
} else {
    linux-* {
        # Build only in debug mode.
        debug_and_release|CONFIG(debug, debug|release) {
            SUBDIRS += qtcreatorcrashhandler
        }
    }
}
move the qtcdebugger tool to an appropriate place 2009-06-04 19:39:48 +02:00			`TEMPLATE = subdirs`
Add a little tool doing the job of 'qmake -project' This creates a .pro from all "source" files below a given directory. As I'd like to use Qt Creator as tool to quickly inspect and navigate "alien" codebases a way to easily set up dummy .pro files is needed. qmake -project takes far too long on projects of the size of Qt itself. 2010-10-29 15:23:13 +02:00
Debugger: Fix interrupting code. - Windows: Always use DebugBreakProcess if Qt Creator is compiled 64bit. Else always use win64interrupt.exe if Qt Creator is a WOW64 application. - Remove redundant code (procinterrupt/hostutils, gdb adapters). - Give interruptProcess an errorMessage parameter such that it can be used by all C++ engines and a proper error is displayed. - Improve error messages. - Build win64interrupt if target architecture is 64 bit (clean tools profile, add a profile), borrowing the check from qtcreatorcdbext.pro. Change-Id: I2a6caf98e46051c49c84e1f3aac4c8d2aba66e8b Reviewed-by: David Schulz <david.schulz@nokia.com> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com> 2012-02-02 09:30:22 +01:00			`SUBDIRS = qtpromaker \`
CodePaster: Add command-line frontend. Code pasting functionality is something that comes in very handy on the shell, so why have it be GUI-only? Change-Id: I4f316769b4ce25e1ab5f90df94ceef33f8478248 Reviewed-by: Tobias Hunger <tobias.hunger@nokia.com> 2012-09-03 14:48:17 +02:00			`qmlpuppet \`
Merge remote-tracking branch 'origin/2.6' Conflicts: qtcreator.qbp src/plugins/qtsupport/baseqtversion.cpp src/tools/tools.pro Change-Id: I43c391328ae747b3dc566f9db2384fedc1a6d0a5 2012-09-26 10:01:04 +02:00			`../plugins/cpaster/frontend \`
Build valgrind-fake on Windows Change-Id: If6252f9a252e9bb0626ec60bdf34fa82cda09bfa Reviewed-by: Christian Kandeler <christian.kandeler@digia.com> 2013-09-08 12:00:49 +03:00			`sdktool \`
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 \`
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			`3rdparty \`
Remove Qt version checks. Qt 5.3 is the minimum requirement these days. Remove all fallback code from sources and project files. Change-Id: If6188a471197acadda4d6baee71804ba1a8026c6 Reviewed-by: Eike Ziller <eike.ziller@digia.com> 2014-08-29 13:18:41 +02:00			`qml2puppet \`
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`
Compile qmldump with debugging helpers Must be compiled during runtime - otherwise, the app may not work with Qt that is compiled with another compiler. Reviewed-by: hjk 2010-09-27 15:51:49 +02:00
Debugger: Fix interrupting code. - Windows: Always use DebugBreakProcess if Qt Creator is compiled 64bit. Else always use win64interrupt.exe if Qt Creator is a WOW64 application. - Remove redundant code (procinterrupt/hostutils, gdb adapters). - Give interruptProcess an errorMessage parameter such that it can be used by all C++ engines and a proper error is displayed. - Improve error messages. - Build win64interrupt if target architecture is 64 bit (clean tools profile, add a profile), borrowing the check from qtcreatorcdbext.pro. Change-Id: I2a6caf98e46051c49c84e1f3aac4c8d2aba66e8b Reviewed-by: David Schulz <david.schulz@nokia.com> Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com> 2012-02-02 09:30:22 +01:00			`win32 {`
WinRT: Enable debugging for local packages. Change-Id: Ic04f1a471f951caf7a79c69cceecb0ebd5d09919 Reviewed-by: hjk <hjk121@nokiamail.com> 2014-04-25 09:20:57 +02:00			`SUBDIRS += qtcdebugger \`
			`wininterrupt \`
			`winrtdebughelper`
Add valgrindfake emulation/testing tool. Merge-request: 260 Reviewed-by: hjk <qtc-committer@nokia.com> 2011-03-04 12:15:18 +01:00			`}`

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			`mac {`
			`SUBDIRS += iostool`
			`}`

Add breakpad This is not activated if breakpad and qt-breakpad is not availiable. 2010-09-09 19:37:01 +02:00			`QT_BREAKPAD_ROOT_PATH = $$(QT_BREAKPAD_ROOT_PATH)`
			`!isEmpty(QT_BREAKPAD_ROOT_PATH) {`
			`SUBDIRS += qtcrashhandler`
Linux: Add a crash handler providing a backtrace for debug builds. Use case: You're working with a debug version of Qt Creator and you're interested in getting a backtrace displayed as soon as Qt Creator crashes without searching for the core file, starting your debugger, ... Once a 'serious signal' (currently SIGILL, SIGFPE, SIGSEGV, SIGBUS, SIGPIPE) is delivered, a popup displays the following debug information: - Qt Creator version (same as in the about dialog) - Kernel version (uname -a) - GNU/Linux Distribution (/etc/lsb-release) - Backtrace (by gdb) Please note that this crash handler is built and used only in debug mode on GNU/Linux. It's solely meant as a convenience tool for the developer. In contrast to the breakpad integration, this crash handler operates 'offline'. There is no network i/o involved. Change-Id: Idcfb1bf1ad68942615ecfe0dffc0d03154455049 Reviewed-by: Christian Kandeler <christian.kandeler@digia.com> Reviewed-by: hjk <qthjk@ovi.com> 2012-07-04 14:16:26 +02:00			`} else {`
			`linux-* {`
			`# Build only in debug mode.`
			`debug_and_release\|CONFIG(debug, debug\|release) {`
			`SUBDIRS += qtcreatorcrashhandler`
			`}`
			`}`
Add breakpad This is not activated if breakpad and qt-breakpad is not availiable. 2010-09-09 19:37:01 +02:00			`}`