It does work after setting CMAKE_C_SOURCE_FILE_EXTENSIONS inside the
override. It should be set in a CMakeDetermineCompiler file though. I'll
add language support for it next.
As a side note, wouldn't it be better to replace
CMake/Modules/CMakeCCompiler.cmake.in:
/set(CMAKE_C_SOURCE_FILE_EXT
I am still facing a problem: The build step is skipped only the link
step is performed (I missed that in the beginning). It seems like the
build step does not have any dependencies.
This is because different file extension are used. I cannot set
CMAKE_C_SOURCE_FILE_EXTENSIONS because I believ
thank you this is exactly what I am looking for. It is working well.
From the documentation:
«It is loaded after CMake’s builtin compiler and platform information
modules have been loaded but before the information is used.»
since CMakeCInformation.cmake:
# compile a C file into an object file
thank you this is exactly what I am looking for. It is working well.
From the documentation:
«It is loaded after CMake’s builtin compiler and platform information
modules have been loaded but before the information is used.»
since CMakeCInformation.cmake:
# compile a C file into an object fi
thank you this is exactly what I am looking for. It is working well.
From the documentation:
«It is loaded after CMake’s builtin compiler and platform information
modules have been loaded but before the information is used.»
since CMakeCInformation.cmake:
# compile a C file into an object fi
On Thu, 2019-08-29 at 18:27 +0100, hex wrote:
> hello community,
>
> CMake builds a C project with gcc -o target_name. I have a compiler
> very similar to GCC and I am trying configure CMake C language for
> it.
>
> The compiler does not support the -o ar
On Fri, Aug 30, 2019, at 1:47 AM, Eric Doenges wrote:
> On 29.08.2019 22:38, fdk17 wrote:
>> On Thu, Aug 29, 2019, at 2:52 PM, Kyle Edwards via CMake wrote:
>>> On Thu, 2019-08-29 at 18:27 +0100, hex wrote:
>>> > hello community,
>>> >
>>> > CMake builds a C project with gcc -o target_name. I ha
