On 01/09/2014 06:08 PM, Stephen Kelly wrote:
The solution would seem to be to create a new compiler id 'QCC'
If the compiler has its own command-line front-end that uses different
flags than the currently detected compiler id, then yes a new id makes
sense.
-Brad
--
Powered by www.kitware.com
On 1/10/2014 9:12 AM, Brad King wrote:
On 01/09/2014 06:08 PM, Stephen Kelly wrote:
The solution would seem to be to create a new compiler id 'QCC'
If the compiler has its own command-line front-end that uses different
flags than the currently detected compiler id, then yes a new id makes
Bill Hoffman wrote:
On 1/10/2014 9:12 AM, Brad King wrote:
On 01/09/2014 06:08 PM, Stephen Kelly wrote:
The solution would seem to be to create a new compiler id 'QCC'
If the compiler has its own command-line front-end that uses different
flags than the currently detected compiler id, then
Hi,
I have this patch:
diff --git a/Modules/Platform/QNX.cmake b/Modules/Platform/QNX.cmake
index 8d45360..58ec112 100644
--- a/Modules/Platform/QNX.cmake
+++ b/Modules/Platform/QNX.cmake
@@ -1,12 +1,10 @@
set(QNXNTO 1)
-# Revise
-# The QNX GCC does not seem to have -isystem so remove the
