QNX: Add missing flags for configurations and artifact creation.

Commit v3.0.0-rc1~111^2 (QNX: Introduce QCC compiler id for that
QNX platform compiler., 2014-01-20) split handling of the QNX QCC
compiler into a separate compiler-id.  That refactoring results in
the QCC compiler not using the CMake-compiler-id "GNU", which means
that the __compiler_gnu macro is no longer executed for it.

Add Compiler/QCC*.cmake modules to define and call the __compiler_qcc
macro and teach it to call __compiler_gnu internally.  Remove the
corresponding pieces from the Platform/QNX*.cmake modules.

It is also necessary to change the language conditional to dereference
the lang macro parameter, which is another bug introduced by the
same commit.  The extra -lang-c++ flag is only necessary when the CXX
compiler is specified as 'qcc' instead of 'QCC' in the toolchain file,
which is why this bug was not noticed before.  The flag is also necessary
in that case when linking in order to find the appropriate standard
libraries.  The flag was not previously added when linking executables,
so linking failed even with CMake 2.8.12 with the lower-case compiler-id.

Co-Author: Brad King <brad.king@kitware.com>
Merge branch 'fix-QCC-compile-flags' into release
Merge branch 'compile-with-cray' into release
KWSys SystemInformation: No SA_RESTART on QNX

QNX not support SA_RESTART signal:

 /* #define SA_RESTART 0x0040 (not supported yet) */

Use it in SystemInformation only if it is defined.
Merge branch 'backport-kwsys-qnx-fix' into release
KWSys 2014-07-18 (65b36ede)

Extract upstream KWSys using the following shell commands.

$ git archive --prefix=upstream-kwsys/ 65b36ede | tar x
$ git shortlog --no-merges --abbrev=8 --format='%h %s' c2a329ce..65b36ede
Bob E (1):
      697b1401 SystemInformation: No SA_RESTART on QNX

Clinton Stimpson (1):
      65b36ede Encoding: Fix testProcess to work with unicode paths.

Steve Dougherty (1):
      5f28a52b Terminal: Fix spelling of 'definitely' in comments

Change-Id: I224745dc0ca9603ff915b727e798ef293c462d8f
Merge branch 'upstream-kwsys' into update-kwsys
CMake Nightly Date Stamp
CMake Nightly Date Stamp
CMake Nightly Date Stamp
Merge topic 'update-kwsys'

6f3e094e Merge branch 'upstream-kwsys' into update-kwsys
d4d1b7f7 KWSys 2014-07-18 (65b36ede)
Merge topic 'fix-QCC-compile-flags'

3151024d QNX: Add missing flags for configurations and artifact creation.
Merge topic 'backport-kwsys-qnx-fix'

cc3248f4 KWSys SystemInformation: No SA_RESTART on QNX
cmTarget: Drop internal cache of link interface usage requirements

These use a huge amount of memory that accumulates as generation
proceeds.  On the Unix Makefiles generator, only GetIncludeDirectories
and GetCompileDefinitions are even called more than once per target
(once for build files, once for dependency scanning preprocessor info).
Another approach will be needed to avoid duplicate computation in the
cases where it does occur.
cmTarget: Drop internal cache of build properties

These use a huge amount of memory that accumulates as generation
proceeds.  On the Unix Makefiles generator, only GetIncludeDirectories
and GetCompileDefinitions are even called more than once per target
(once for build files, once for dependency scanning preprocessor info).
Another approach will be needed to avoid duplicate computation in the
cases where it does occur.
cmTarget: Remove duplicate link interface map

No target is both imported and not imported so we do not need separate
link interface maps for them.
cmTarget: Refactor link interface map storage

Convert LinkInterfaceMapType and LinkImplMapType to nested maps that
index on configuration first and 'head' target second.
cmTarget: Re-order link interface map lookup logic

In GetLinkInterface, GetLinkInterfaceLibraries, and
GetImportLinkInterface, lookup the HeadToLinkInterfaceMap for the
current configuration first, and then index it by head target.  In
GetLinkImplementationLibrariesInternal, lookup the
HeadToLinkImplementationMap for the current configuration first, and
then index it by head target.
cmTarget: Move ComputeLinkImplementation* to internals

There are no external callers, and this will allow the methods to see
the full OptionalLinkImplementation internal structure.
Genex: Track whether an expression depends on the 'head' target