Closed 1ace closed 2 months ago
Hey, thank you for this issue! I'm not sure why it was skipped, but I will investigate it
It took a while, but if this works: https://copr.fedorainfracloud.org/coprs/jcwasmx86/Swift-MesonLSP/build/8062051/ you will have fancy aarch64 builds :)
I hope it's not inappropriate to ask: Have you already used mesonlsp somewhat extensively? If yes, do you have a few spare seconds to fill out this survey/telemetry information: https://github.com/JCWasmx86/mesonlsp/discussions/104
It seems like the build completed successfully
Thanks! I installed it (and deleted my local build), and I can confirm it works :+1:
I hope it's not inappropriate to ask: Have you already used mesonlsp somewhat extensively? If yes, do you have a few spare seconds to fill out this survey/telemetry information: #104
I have discovered this project on friday and I tried it for the first time this morning, just before posting this issue, and I haven't worked on meson files today (other than just discovering what the lsp provides here for a few minutes), so I wouldn't exactly call my use "extensive" 😅
I'll post something on #104 now, and try to remember to come back once I have more feedback 🙂
Describe the bug
Looking at the latest build for instance: https://copr.fedorainfracloud.org/coprs/jcwasmx86/Swift-MesonLSP/build/8034049/ The two
x86_64
builds have "succeeded", while the twoaarch64
builds were "skipped".This can be confirmed by looking at the artifacts available for the two
fedora-$releasever-aarch64
in https://download.copr.fedorainfracloud.org/results/jcwasmx86/Swift-MesonLSP/; they contain nothing.Expected behavior
The aarch64 builds should not be disabled/skipped/etc. so that those of us on an ARM laptop get to use
mesonlsp
too :PAdditional context
Building it by hand (
meson setup
+meson compile
) yields a working binary, so there is no need to disable aarch64 in case it was thought to be non-functional :)(I deleted the other sections as they are only relevant if the bug is in mesonlsp itself)