Cross-Compile Rust Application for Linux, Windows, and Android Termux on EndeavourOS

- by mahmood 
sudo pacman -S rustup
rustup default stable
# 🐧 Linux (Already default, but ensuring native architecture toolchain)
rustup target add x86_64-unknown-linux-gnu

# 🪟 Windows (Using GNU/MinGW ABI for easy cross-compiling from Linux)
rustup target add x86_64-pc-windows-gnu

# 🤖 Android / Termux (armv8 / 64-bit ARM)
rustup target add aarch64-linux-android

# 🤖 Android / Termux (armv7 / 32-bit ARM)
rustup target add armv7-linux-androideabi

Install System Cross-Linkers

sudo pacman -S mingw-w64-gcc
yay -S android-ndk

Configure Cargo Linkers

Cargo needs to know which linker to pull when you pass a --target flag. Create or edit your global Cargo configuration file at ~/.cargo/config.toml (or create one locally inside your project folder) and add the following mapping:

# ==================== 🪟 WINDOWS TARGET ====================
[target.x86_64-pc-windows-gnu]
linker = "x86_64-w64-mingw32-gcc"
ar = "x86_64-w64-mingw32-ar"

# ==================== 🤖 ANDROID ARMV8 (64-bit ARM) ====================
# This matches: aarch64-linux-android35-clang
[target.aarch64-linux-android]
linker = "/opt/android-ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android35-clang"

# ==================== 🤖 ANDROID ARMV7 (32-bit ARM) ====================
# This matches: armv7a-linux-androideabi35-clang
[target.armv7-linux-androideabi]
linker = "/opt/android-ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/armv7a-linux-androideabi35-clang"

⚠️ Important NDK Note: Double-check the path inside /opt/android-ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/. Depending on the NDK version installed, the API version number suffix at the end of the compiler name (e.g., android34-clang) might vary (like android31-clang). Change it to match what is present in your folder.

Fix the Critical Android Linker Issue

Rust cross-compilation for Android has a historic quirk: even when you specify the custom clang compiler executable above as your linker, Cargo’s internal driver often tries to pass arguments to it using standard GNU tools (strip, ar) rather than the LLVM tools inside the NDK.

To prevent compilation failures when building complex dependency crates, you must let your terminal environment know where the NDK binaries live. Add these exports to your shell script or run them right before building:

export ANDROID_NDK_HOME="/opt/android-ndk"
export PATH="$ANDROID_NDK_HOME/toolchains/llvm/prebuilt/linux-x86_64/bin:$PATH"

If you are using the Fish Shell, run these lines instead to set them up:

set -gx ANDROID_NDK_HOME /opt/android-ndk
set -gx PATH $ANDROID_NDK_HOME/toolchains/llvm/prebuilt/linux-x86_64/bin $PATH

Building the App

# 🐧 Build for Linux
cargo build --release

# 🪟 Build for Windows (Generates a .exe in target/x86_64-pc-windows-gnu/release/)
cargo build --target x86_64-pc-windows-gnu --release

# 🤖 Build for Termux 64-bit (armv8)
cargo build --target aarch64-linux-android --release

# 🤖 Build for Termux 32-bit (armv7)
cargo build --target armv7-linux-androideabi --release

 

Run Git Commands with a Specific SSH Key

- by mahmood 
GIT_SSH_COMMAND="ssh -i /home/user/keys/project_private_key" git [any-command]

Making it Persistent for Your Session

# 1. Lock in the key for this terminal tab
export GIT_SSH_COMMAND="ssh -i /home/user/keys/project_private_key"

# 2. Run as many commands as you want freely!
git fetch
git status
git push origin feature-branch

 

Install Ghostty and Fish on EndeavourOS

- by mahmood 
sudo pacman -Syu ghostty fish

Set Fish as Your Default Shell

chsh -s $(which fish)

Configure Ghostty to Launch Fish Natively

mkdir -p ~/.config/ghostty
touch ~/.config/ghostty/config
nano ~/.config/ghostty/config
# --- Shell Execution ---
command = /usr/bin/fish

window-inherit-working-directory = false

# --- Visual Tuning (Optional Suggestions) ---
font-family = "JetBrainsMono Nerd Font"
font-size = 11
theme = dark:tomorrow-night,light:tomorrow-day
window-padding-x = 10
window-padding-y = 10
nano ~/.config/fish/config.fish

Add this snippet to the top of the file to force Ghostty’s terminal environment mapping:

if set -q GHOSTTY_RESOURCES_DIR
    source "$GHOSTTY_RESOURCES_DIR/shell-integration/fish/vendor_conf.d/ghostty-shell-integration.fish"
end

First-Time Fish Setup

fish_config

 

 

Disable Windows Wi-Fi Auto-Disconnect on Poor Networks

- by mahmood

Using Registry Editor (regedit) – for all Windows Editions

  1. Press Windows + R, type regedit, and press Enter to open the Registry Editor.

  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator. If the NetworkConnectivityStatusIndicator key does not exist, right-click on the Windows key, select New > Key, and name it exactly that.

  3. In the right pane, right-click and select New > DWORD (32-bit) Value.

  4. Create the following two values and set their data to 1:

    • NoActiveProbe

    • DisablePassivePolling

  5. Restart your computer for the changes to take effect.

Disable WLAN AutoConfig

This method uses a command to forcefully stop the auto-configuration feature.

  1. Search for “Command Prompt”, right-click it, and select Run as administrator.

  2. To disable the automatic configuration, run: netsh wlan set autoconfig enable=no interface="Wi-Fi".

  3. To re-enable it later, simply change no to yes in the same command.

Modify the hosts File

This method is complex and not recommended for the average user as it involves running a local web server to “trick” Windows into thinking the NCSI tests are passing.

  1. Edit the hosts file (C:\Windows\System32\drivers\etc\hosts) and add these lines: 127.0.0.1 www.msftconnecttest.com and 127.0.0.1 www.msftncsi.com.

  2. Run a local web server (like XAMPP) that responds to these requests.

Share your PC’s Internet to the Ubuntu Server through SSH

- by mahmood

Best case: your PC can SSH into the Ubuntu server

Run this on your PC:

ssh -N -R 127.0.0.1:1080 ubuntu_user@UBUNTU_SERVER_IP

This creates a SOCKS proxy on the Ubuntu server at:

127.0.0.1:1080

Traffic from the Ubuntu server will go through SSH and exit from your PC’s internet connection.

On the Ubuntu server, test it:

curl --proxy socks5h://127.0.0.1:1080 https://ifconfig.me

Other case: Ubuntu server can SSH into your PC

Then run this on the Ubuntu server:

ssh -N -D 127.0.0.1:1080 pc_user@PC_IP
curl --proxy socks5h://127.0.0.1:1080 https://ifconfig.me

More reliable option: use an HTTP proxy through SSH

Run an HTTP proxy on your Windows PC

For example, if you already use one of these apps:

App Common HTTP / mixed proxy port
v2rayN 10809 or similar
Clash Verge / Clash for Windows 7890
NekoRay / NekoBox usually configurable

Use the app’s HTTP or mixed proxy port.

ssh -N -R 127.0.0.1:1080:127.0.0.1:7890 ubuntu_user@UBUNTU_SERVER_IP

 

Disable SmartScreen via Group Policy in Windows 11

- by mahmood

Open the Local Group Policy Editor: Press Windows + R, type gpedit.msc into the Run dialog, and click “OK”.

Navigate to the Policy: Go to the following path in the left panel:
Computer Configuration → Administrative Templates → Windows Components → File Explorer
(Note: In some Windows 11 versions, this may be named “Windows Explorer” instead.)

Open the Policy Setting: In the right panel, double-click “Configure Windows Defender SmartScreen”.

Disable SmartScreen: In the window that opens, select the Disabled option and click Apply and then OK to save the changes.

Create an SSH User with a non-interactive Shell

- by mahmood

Create the Restricted System User

sudo useradd -r -s /bin/false -m -d /home/proxyuser proxyuser

Set Up Authentication

sudo passwd proxyuser

Configure SSH Daemon

sudo nano /etc/ssh/sshd_config
Match User proxyuser
    AllowAgentForwarding no
    AllowTcpForwarding yes
    X11Forwarding no
    PermitTTY no
    ForceCommand /bin/false

Restart the SSH Service

sudo systemctl restart ssh
# or
sudo systemctl restart sshd