clangd and yq x86_64 and android compatibility support.

[OurCodeBase]

Changes

• clangd server's target is changed from linux_x64_gnu to linux_x64 to support on x86_64 and android based PCs.
• yq server's targets are changed from linux_x64_gnu and linux_arm64_gnu to linux_x64 and linux_arm64 to support on x86_64 and android based PCs.
• yq server's gnu linux distro targets are shifted under openbsd targets to kill conflicts.

Checklist before requesting a review

• I have successfully tested installation of the package.
• I have successfully tested the package after installation.

[williamboman]

These have a _gnu suffix because the compiled binaries are dynamically linked using the GNU linker. "GNU support" is determined by the mason.nvim client. If you're on a system that supports executing GNU binaries as-is (i.e. no nix-ld or something like that) but it's not getting recognized by Mason I'd be more interested in addressing that in mason.nvim than modifying the package like this.

[OurCodeBase]

These have a _gnu suffix because the compiled binaries are dynamically linked using the GNU linker. "GNU support" is determined by the mason.nvim client. If you're on a system that supports executing GNU binaries as-is (i.e. no nix-ld or something like that) but it's not getting recognized by Mason I'd be more interested in addressing that in mason.nvim than modifying the package like this.

Thanks for the response,

I'm using debian for development and sometimes i use termux on my android phone. I've tested this and it's working fine on both of them.

Can I use the forked version by default?

[robertkirkman]

Hi, I have created a port of codelldb to Android that is compiled and linked with the Android bionic C library and linker.

I've deployed a first revision of codelldb for Android into the Termux package repositories, but I am also working on a second revision of it here that has several things fixed:

• addpkg(x11/codelldb): split from vsix-package-codelldb termux/termux-packages#25663

I noticed that in this repository, there's an instance of a codelldb package,

mason-registry/packages/codelldb/package.yaml

Line 4 in 9c8dd78

homepage: https://github.com/vadimcn/vscode-lldb

however, unfortunately this repository doesn't support Android, and OpenVSIX doesn't support Android either, so I am confused about the best way to proceed with distributing the functioning build of the Rust code of codelldb into an Android Bionic C library executable that I have created.

I am pretty sure that I will probably be able to distribute all the necessary packages for codelldb on Android through the Termux hosting infrastructure,

I'm just explaining the situation that I'm in here so that it's clear what I have been doing regarding the situation of using a different sort of "editor plugin" that is also here, on Android.

I was thinking that maybe, if this repository had support for an "Android" target of some kind, it should most likely be "linux_x64_android", etc, and "linux_x64_gnu" should be left unchanged, since they are relatively cleanly separated operating systems that both have a Linux kernel, especially when Termux is considered (which is the primary distribution host of Neovim for Android and the dependencies of that)?

[github-actions]

This PR has been automatically marked as stale.
If this issue is still relevant, please leave any comment, and it will be kept open.