Dylan Baker <[email protected]> writes: > [ Unknown signature status ] > Quoting Eric Anholt (2018-06-07 14:34:02) >> Dylan Baker <[email protected]> writes: >> >> > The reason we restrict the use of ASM when cross compiling is that there >> > is a C based generator (mtypes) that must be run as part of the build >> > process, and it must be built for the host architecture. In the case of >> > an x86 host and an x86_64 build machine this is possible as long as the >> > host and build OSes are the same (ie, not Windows -> Linux). >> > >> > This also makes the commit message a bit more generic than it previously >> > was. >> >> Given that the igt meson build has been running some of my >> cross-compiled arm binaries under qemu during its build process, I >> actually don't think we need to restrict running matypes compiled for >> the host. > > I have a todo about that actually. Really the only cases we need to restrict > are > x86 -> x86_64 and !x86* -> x86*; (since only x86* uses gen_matypes). I just > haven't had time to test using an exe_wrapper for that purpose, and meson > doesn't enforce that you have an exe_wrapper, so we still need to disable the > assembly if you don't have one.
I would be on board with just requiring an exe_wrapper for cross builds on archs with asm -- why would you want to build Mesa without asm?
signature.asc
Description: PGP signature
_______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
