this post was submitted on 17 Sep 2026
273 points (99.6% liked)

Linux

19674 readers
21 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] warmaster@lemmy.world 1 points 1 month ago (1 children)

Is there an x86 build of every app?

[โ€“] kewjo@lemmy.world 1 points 1 month ago

no but the dev controls it. if the dev is using the ndk and the dev is not doing the extra step of disabling/configuring it there should be in "fat" apk with each binary for each platform according to the docs. then the installer can figure out which version to use.

the x86(/_64) version is used for Chromebooks i believe. some devs will split the apk if they configured it to reduce size so you would need to specifically go get an x86 apk version.

the cases where a dev would disable it is if they only want to support specific instructions that might be platform specific or say a library they use doesn't support target ABIs