Open Wunkolo opened 6 months ago
Stubbed the Null CPU-backend on ARM64 to get the main application running.
The new Arm64 backend(a64
) will be added in a separate PR.
Dear @Wunkolo, congrats on this great leap in (portable) Xbox emulation!
Perhaps you could point me towards my missing puzzle piece. I forked your arm64 branch and applied your ffmpeg changes, however three SDL libraries refuse to be linked.
git clone -b 'arm64-backend' --single-branch https://github.com/Wunkolo/xenia/
cd xenia
git submodule update --init --recursive
./xb.bat build --config=release
Just pushed a fix that should address the SDL linkage issue!
Hello @Wunkolo, well it's a
but no (running) Waltz 😒:
Have you (already) adapted the paths and filenames to ARM yet?
Cause the build path is "still" \build\bin\Windows-x86_64\Release\
and there is "still" a xenia-cpu-backend-x64.lib
generated.
Thanks for the quick reply and ongoing efforts.
You are currently still compiling an x64 build at the moment. It will still compile x64 by default. If you want to build the ARM version you have to set the build-target to the ARM64 version when building from Visual Studio. You can also use this command to specify the arm64 build.
./xb build --arch=arm64
When compiled, build artifacts will be found within the build\bin\Windows-ARM64
folder.
It will still compile x64 by default. If you want to build the ARM version you have to set the build-target to the ARM64 version when building from Visual Studio.
That makes a lot of sense.
Restarting the batch file with:
./xb.bat build --arch=arm64 --config=release
leads to ARM64 results:
But a few libraries (SPIRV & ImGui) complain,
Let me fire up the Visual Studio GUI, as that will output all English text results.
Here are the three failed projects (xenia-hid-demo, xenia-gpu-shader-compiler & xenia-app
)
and their two culprits (imgui.lib & glslang-spirv.lib
):
Not sure what's happening here in particular. I can't seem to recreate it locally in Debug or Release in the case that these are LTO issues.
Separates the
Windows
platform intoWindows-x86_64
andWindows-ARM64
.This is dependent on https://github.com/xenia-project/FFmpeg/pull/8
Windows-x86_64
builds as usual and is the default target whileWindows-ARM64
breaks in expected x64-specific areas.Implements some basic build support for Windows on Arm: