Here's a basic one, with which I managed to compile & link simple stuff - disclaimer : based on the ideas found in a google search for "keil" "cmake". I only tested on linux with wine. God is that compiler invocation ugly :)
Example project I used (with dummy foo.c/bar.c/"space out" subfolder not
attached) :
cmake_minimum_required(VERSION 3.14)
project(foo C)
add_executable(foo
foo.c
"space out/bar.c"
)
target_include_directories(foo
PRIVATE
"${CMAKE_CURRENT_SOURCE_DIR}"
"${CMAKE_CURRENT_BINARY_DIR}"
"space out"
)
target_compile_options(foo
PRIVATE
COMPACT
)
target_compile_definitions(foo
PRIVATE
hello
toto="1"
)
Best,
Jean-Michaël
On Tue, Jun 18, 2019 at 1:44 PM Denis Shienkov <denis.shien...@gmail.com>
wrote:
> > Matthew Woehlke
>
> > The difference between QBS and CMake is like the difference between a
> > bright-eyed recruit just out of school and a grizzled veteran.
>
> Ok, then, please, provide a simple toolchain file to use e.g. a bare-metal
> KEIL C51 [1] compiler. And then, we will to see, how it does in QBS and in
> CMake. Who will win then?
>
> PS: Of course, my question does not related to Qt build tool, it is a common
> question. :)
>
> [1] http://www.keil.com/support/man/docs/c51/c51_cm_cmdprompt.htm
>
> BR,
>
> Denis
>
> _______________________________________________
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
>
Keil.cmake
Description: Binary data
KeilLink.cmake
Description: Binary data
KeilCompile.cmake
Description: Binary data
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
