[Development] Proposing CMake as build tool for Qt 6
denis.shienkov at gmail.com
Wed Jun 19 10:49:11 CEST 2019
WOW, many thanks.. :)
But, as I can see, with CMake it is very over-complicated (as for me as a
noob). For this I need to
waste a lot of time to search in google, on stackoverflow and etc. I think,
that even a week is not
enough for this (to know for all CMake keywords and features which are
required to make a custom
cross-toolchain). Unlike to QBS, where I spent a hour to *create* and
*debug* of a custom toolchain
(basically to study of a compiler datasheet with it commands).
But, OK, many thanks for the example, anyway. :)
ср, 19 июн. 2019 г. в 10:44, Jean-Michaël Celerier <
jeanmichael.celerier at gmail.com>:
> 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"
> 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)
> "space out/bar.c"
> "space out"
> On Tue, Jun 18, 2019 at 1:44 PM Denis Shienkov <denis.shienkov at gmail.com>
>> > 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  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. :)
>>  http://www.keil.com/support/man/docs/c51/c51_cm_cmdprompt.htm
>> Development mailing list
>> Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development