> If building with MSVC tools, yes you're right that armasm.exe/armasm64.exe > takes a different syntax. But the gas-preprocessor tool (which is picked up > automatically by our configure, one just needs to make sure it's available) > handles expanding all the macros and rewriting directives into the armasm > form, and feeding it to the armasm tools. Works fine and have done so for > years. There's even a wiki page which tries to explain how to do it (although > it's probably outdated in some aspects), see > https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT. >
I went with the instructions in doc/platform.texi and that did not work at all, It even tried to use cl.exe to compile the assembler files! > All of these run with full assembly optimizations enabled. So please don't > tell me that our assembly doesn't work on windows on arm, because it does, > and it has for years. > My apologies. I’ll correct to: it doesn’t work using the instructions shipping with the source code (as far as I can tell) :) _______________________________________________ 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".
