[Development] CMake && QtCreator cross-compilation for ARM fails

[Christian Gagneraud]

Hi Kevin,

On Fri, 14 Dec 2018 at 00:54, Kevin Kofler <kevin.kofler at chello.at> wrote:
> Bootstrapping QMake has always been the least pleasant part of the Qt build
> process.

Yes, i think we all agree on that one.

> I am looking forward to this bootstrapping hack going away by just using
> CMake.

So you want to replace a bunch of scripts with another bunch of
scripts, and magically the maintenance burden will be gone?
My bet is that it will never happen, you'll still need the power of
perl, python or javascript to do the "dirty job", CMake is not
expressive enough, by design.

> > Can you point me to something that shows the Qt "project" contributing
> > to the Qt "company" on that very particular topic?
> The Qt Project is largely just the Qt Company when it comes to such core
> tasks.

It seems that you cannot point me to something tangible.

> > The Qt Company has been looking for "employees" to work on Qbs for
> > month before dropping it, apparently nobody responded, or something...
>
> Then that would pretty much explain why they cannot maintain it in the long
> run.

You are right, and it would be nice to have official statements on
that. What did really happen?

> > read that one:
> > https://cmake.org/cmake/help/latest/manual/cmake-generator-expressions.7.html#output-expressions
>
> That is a powerful feature. And you don't have to use it if you don't need
> it. Most CMake files actually do not need or use output expressions.

It's not just the output expressions, the whole page "smells bad".
Take '$<COMMA>' for example, it reminds me of m4, make and qmake, like
we haven't moved away from the old daemons.

> > And read that again and again, until you brain says: 'Actually, CMake
> > is "crap"!'
>
> My brain refuses to enter this infinite loop. ;-)

Mine too. :-p

Chris