src/tools/tools.pro

TEMPLATE = subdirs

SUBDIRS = qtpromaker \
     qmlpuppet \
     ../plugins/cpaster/frontend

win32 {
    SUBDIRS += qtcdebugger
    # win64interrupt only make sense for 64bit builds
    ENV_CPU=$$(CPU)
    ENV_LIBPATH=$$(LIBPATH)
    contains(ENV_CPU, ^AMD64$) {
        SUBDIRS += win64interrupt
    } else:isEmpty(ENV_CPU):contains(ENV_LIBPATH, ^.*amd64.*$) {
        SUBDIRS += win64interrupt
    }
} else {
    SUBDIRS += valgrindfake
}

QT_BREAKPAD_ROOT_PATH = $$(QT_BREAKPAD_ROOT_PATH)
!isEmpty(QT_BREAKPAD_ROOT_PATH) {
    SUBDIRS += qtcrashhandler
}
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 \`
			`../plugins/cpaster/frontend`
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 {`
			`SUBDIRS += qtcdebugger`
			`# win64interrupt only make sense for 64bit builds`
			`ENV_CPU=$$(CPU)`
			`ENV_LIBPATH=$$(LIBPATH)`
			`contains(ENV_CPU, ^AMD64$) {`
			`SUBDIRS += win64interrupt`
			`} else:isEmpty(ENV_CPU):contains(ENV_LIBPATH, ^.amd64.$) {`
			`SUBDIRS += win64interrupt`
			`}`
			`} else {`
Add valgrindfake emulation/testing tool. Merge-request: 260 Reviewed-by: hjk <qtc-committer@nokia.com> 2011-03-04 12:15:18 +01:00			`SUBDIRS += valgrindfake`
			`}`

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`
			`}`
Build fix for tools We have to check for Qt Versions and private headers to build qmlpuppet. Reviewed-by: Kai Koehne 2010-11-26 14:24:44 +01:00