diff options
author | Rohan McGovern <rohan.mcgovern@nokia.com> | 2011-06-23 10:48:33 +0200 |
---|---|---|
committer | Qt by Nokia <qt-info@nokia.com> | 2011-11-15 07:21:48 +0100 |
commit | 4e014ace452af8f1e22b95ba22d112fc2419ec6d (patch) | |
tree | 8a891f75e7cfcd194580fecb1db64479ab3de01b /mkspecs/features/testcocoon.prf | |
parent | b4d23e61ed19c770caf6b993a8ab0e4474d3f417 (diff) |
Integrate testcocoon support into Qt build system.
To instrument a Qt application or library with the TestCocoon coverage
tool, do `CONFIG+=testcocoon' in the application .pro file.
To instrument Qt itself with testcocoon, use the `-testcocoon' configure
option.
Change-Id: Ie77109a078d11ea51f7a073621e0df9c752c44ae
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
Diffstat (limited to 'mkspecs/features/testcocoon.prf')
-rw-r--r-- | mkspecs/features/testcocoon.prf | 57 |
1 files changed, 57 insertions, 0 deletions
diff --git a/mkspecs/features/testcocoon.prf b/mkspecs/features/testcocoon.prf new file mode 100644 index 0000000000..e6ad733540 --- /dev/null +++ b/mkspecs/features/testcocoon.prf @@ -0,0 +1,57 @@ +# +# Tested with TestCocoon 1.6.14 +# + +load(resolve_target) + +# Retrieve the target basename +TARGET_BASENAME = $$basename(QMAKE_RESOLVED_TARGET) + +# Configure testcocoon for a full instrumentation - excluding the moc, ui and qrc files from the instrumentation +# --cs-output defines the name to give to the execution report (.csexe). +TESTCOCOON_COVERAGE_OPTIONS = \ + --cs-qt4 \ + --cs-exclude-file-regex=\'(^|[/\\\\])ui_.*\\.h\$\$\' \ + --cs-exclude-file-regex=\'(^|[/\\\\])(qrc|moc)_.*\\.cpp\$\$\' \ + --cs-exclude-file-regex=\'.*\\.moc\$\$\' \ + --cs-exclude-file-regex=\'.*\\.g\$\$\' \ + --cs-output=\'$$TARGET_BASENAME\' # name of the csexe file (execution report) + +# The .csmes file should be placed alongside the .so or binary. +# Unfortunately, testcocoon has no option to specify the output directory, +# so we must move it into place if a custom destdir was used. +# We don't move applications' csmes because some qt applications (tools, examples) +# are using DESTDIR in some cases but always alongside target.path, so the binary +# is built directly in target.path and there is no need to move the csmes. +!isEmpty(DESTDIR):contains(TEMPLATE, lib) { + !isEmpty(QMAKE_POST_LINK):QMAKE_POST_LINK = $$escape_expand(\\n\\t)$$QMAKE_POST_LINK + QMAKE_POST_LINK = -$(MOVE) $${TARGET_BASENAME}.csmes $${QMAKE_RESOLVED_TARGET}.csmes$$QMAKE_POST_LINK +} + +QMAKE_CLEAN += *.csexe *.csmes + +# The compiler/linker is replaced by the coveragescanner which is named after the name of the +# compiler/linker preceded by cs (ie gcc is replaced by csgcc). +# Testcocoon options defined in TESTCOCOON_COVERAGE_OPTIONS are added as argument to the coveragescanner (ie csgcc). +# In practice they are added as compiler/linker flags. + +*-g++* { + QMAKE_CXX ~= s/(\\S*g\\+\\+)/cs\\1/ + QMAKE_CC ~= s/(\\S*gcc)/cs\\1/ + QMAKE_LINK ~= s/(\\S*g\\+\\+|\\S*gcc)/cs\\1/ + QMAKE_AR ~= s/(\\S*ar)/cs\\1/ + QMAKE_AR += $$TESTCOCOON_COVERAGE_OPTIONS +} else { + error("Non-gcc qmake specs not supported by TestCocoon integration yet") +} + +QMAKE_CFLAGS += $$TESTCOCOON_COVERAGE_OPTIONS +QMAKE_CXXFLAGS += $$TESTCOCOON_COVERAGE_OPTIONS +QMAKE_LFLAGS += $$TESTCOCOON_COVERAGE_OPTIONS + +unix { + QMAKE_LFLAGS += --cs-libgen=-fPIC +} + +unset(TARGET_BASENAME) +unset(TESTCOCOON_COVERAGE_OPTIONS) |