a lot of (maybe all) packages depending on qt6 fail to cross-compile #3035
Comments
|
every single one of them fails to cross compile, yes. it's not unexpected and there's nobody interested in making it work (since cross compiling is not a primary focus and it being broken is not seen as a bug) |
|
if you know what magic to pass to cmake for qt cross to work and for it to use 'host moc/uic , etc tools' then maybe it's fixable |
|
oh, i understand, sorry for making the issue |
|
you can keep it open but i don't think i'll make any attempt at fixing it (anybody else is free to though) (also there is probably a lot more other packages that fail to crosscompile, it's not something unique to qt6 because i don't usually test cross at all) |
|
they should perhaps be marked as !cross, but i think marking things fundamentally uncrossable because 'all are qt' is a bit bad, since then there's a lot of work to later unset it if that (single) issue is fixed. it's easier to just not touch it even though it's known-broken.. (i think the same thing for gobject-introspection- if they add an actual fix upstream then we have to remove !cross in 100 places, which isn't super meaningful) |
the packages i've tested fail during the configure stage due to it trying to launch a binary from a foreign architecture, even if the equivalent for the host architecture is installed
different packages seem to be failing in different stages, for example in the AUTOMOC stage (example: main/openmw) or while executing ECMQueryQt.cmake (example: main/karchive)
i've attached a log from my attempts of building these two packages
here's a list of packages i've attempted and failed to crossbuild:
log for main/openmw (target aarch64, host x86_64)
log for main/karchive (target riscv64, host x86_64)
The text was updated successfully, but these errors were encountered: