On Mon, Mar 30, 2020 at 1:00 PM Derek Buitenhuis <derek.buitenh...@gmail.com> wrote: > On 07/03/2020 15:32, David Michael wrote: > > Using a compiler with a different host triplet is considered > > cross-compiling, even when it is for the same architecture as the > > build system. With such a cross-compiler, it is still valid to > > optimize builds with --cpu=host. Drop the condition that aborts in > > this case, since a cross-compiler for an incompatible architecture > > will fail with -mtune=native anyway. > > Is there a reason you would set the cross-prefix instead of just the --cc, > etc. > when compiling natively?
I want everything to use the cross-prefixed versions since those tools are configured to build software in a sysroot using a different set of compiler features than software in the minimal build root. I am using the same process as when cross-compiling OS images for other incompatible architectures; configuring tuning for the build system's CPU is just another valid use of this setup. Thanks. David _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
