diff options
| author | Martin Ejdestig <mejdestig@luxoft.com> | 2020-09-07 08:51:37 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-07 15:51:37 +0900 |
| commit | f71aea01d44dc48f711b115f7ae90bb421958438 (patch) | |
| tree | e621eb0ffbdde29bc8fa6bed1d6e257b261993b2 | |
| parent | 5843a3f6211d002c4859533ff7ce1791f09105a4 (diff) | |
| download | DLT-daemon-f71aea01d44dc48f711b115f7ae90bb421958438.tar.gz | |
Modify CMAKE_C_COMPILER check for QNX to accept "qcc" (#246)
nto-qnx matches architecture "sub-binaries" for qcc, but can also invoke
with qcc binary and specify architecture. The CMake documentation has an
example for a QNX toolchain file that sets CMAKE_C_COMPILER to qcc, so it
is probably very common. See:
https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html#cross-compiling-for-qnx
Not sure why this check is needed. (Is qcc really the only compiler that
can be used to build for QNX?) An alternative could be to remove it
completely.
Signed-off-by: Martin Ejdestig <mejdestig@luxoft.com>
| -rw-r--r-- | CMakeLists.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CMakeLists.txt b/CMakeLists.txt index 3020e1e..850dbcf 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -136,7 +136,7 @@ if(WITH_DLT_USE_IPv6) add_definitions(-DDLT_USE_IPv6) endif() -if(WITH_DLT_QNX_SYSTEM AND NOT "${CMAKE_C_COMPILER}" MATCHES "nto-qnx") +if(WITH_DLT_QNX_SYSTEM AND NOT "${CMAKE_C_COMPILER}" MATCHES "nto-qnx|qcc") message(FATAL_ERROR "Can only compile for QNX with a QNX compiler.") endif() |