[Development] moc output from non-local tool build

Thiago Macieira thiago.macieira at intel.com
Mon Sep 13 22:13:29 CEST 2021

On Monday, 13 September 2021 11:21:37 PDT Thiago Macieira wrote:
> Your way is easier on the packagers, though, since the cross-compilations
> are usually not critical content, but the host/native Qt is. But I don't
> think it's the typical scenario for cross-compiling. People usually
> download the sources in order to cross-compile Qt with their device's
> toolchain and they'd like to use the system's Qt to help bootstrap. The
> system's Qt is usually older.

Ah, but for embedded device targets, one usually wants the best possible, so 
depending on your distro's older and crappier moc is not a good idea.

Sounds to me like we should do both, with a 2-year sliding window of 
compatibility. My current changes require no extra effort (they're done 
anyway, will push soon).

Adding the version arguments to the tools requires a bit more effort.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering

More information about the Development mailing list