80f6d7862c
stack-protector-strong gives performance benefits over stack-protector-all and is still checking more than -stack-protector, so seems to be a good middle way and we want to use it when it is there. The -shared option for the compiler (not the linker) prevents a RIM internal version of qcc from forcing -fPIE, and should not harm in general when set. In addition, add a method "compilerSupportsFlag" for Windows as is present in the Unix configure script. Change-Id: Iba300e9cb82f34043e7b36f8e45287a1aed2a1a5 Original-patch-by: Greg Bentz Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
19 lines
410 B
Plaintext
19 lines
410 B
Plaintext
#
|
|
# qmake configuration for blackberry x86 systems
|
|
#
|
|
|
|
load(qt_config)
|
|
|
|
DEFINES += Q_OS_BLACKBERRY
|
|
CONFIG += blackberry
|
|
LIBS += -lbps
|
|
|
|
# Blackberry also has support for stack smashing protection in its libc
|
|
contains(QT_CONFIG, stack-protector-strong) {
|
|
QMAKE_CFLAGS += -fstack-protector-strong
|
|
} else {
|
|
QMAKE_CFLAGS += -fstack-protector -fstack-protector-all
|
|
}
|
|
|
|
include(../common/qcc-base-qnx-x86.conf)
|