Conversation
headius
force-pushed
the
armv5_ci
branch
4 times, most recently
from
280e233 to
d7f3a5d
Compare
|
@jcharaoui @TobiX Hey there folks! I entered into this little quest to try to get armv5 builds working again in CI, but now I'm confused how it was ever supported. In #95 @TobiX added a platform matrix to do native builds on several Linux platforms, including "linux-arm-v5". I don't recall if it worked then, but it stopped working at some point. The changes here made that build work again, but the resulting jar file uses the platform "arm", which would conflict with other builds for armv7. In #131 @jcharaoui submitted fixes for the armel platform, which perhaps tested correctly when built on that platform. But I can find no evidence that we ever managed to actually ship armv5/armel support in the Maven artifacts, since there's two conflicting platforms using the same platform name. So I'm wondering... perhaps we should have added a separate platform name for armel and used that for the native builds and internally to load them? Can you help me sort this out? |
* Use trixie * Use default-jdk for armel and riscv64 * Clean up build script a bit
|
FWIW I see that there's official Debian support for Loongarch, so I'd like to get those builds working too... |
1 participant
No description provided.