This guide explains how to compile XyNginC (XNCP) from source code. This is useful if you are using a non-standard architecture (like ARM64/Raspberry Pi), want to contribute to development, or simply prefer to build your own binaries.
To build XNCP, you need the Rust programming language and its package manager, Cargo.
The recommended way to install Rust is via rustup:
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | shFollow the on-screen instructions (default installation is usually fine). After installation, restart your shell or run:
source "$HOME/.cargo/env"Verify the installation:
rustc --version
cargo --versionXNCP relies on OpenSSL. You need to install the development packages for your system.
Ubuntu/Debian/Kali:
sudo apt update
sudo apt install build-essential libssl-dev pkg-configCentOS/RHEL:
sudo yum groupinstall "Development Tools"
sudo yum install openssl-develgit clone https://github.com/Nehonix-Team/xynginc.git
cd xyngincNavigate to the core directory where the Rust code resides:
cd coreBuild the project in release mode (optimized for performance):
cargo build --releaseThis process may take a few minutes as it downloads dependencies and compiles the code.
Once the build completes successfully, the binary will be located at:
./target/release/xyngincTo install your custom-built binary, simply move it to your system's binary path:
sudo mv ./target/release/xynginc /usr/local/bin/Check that the installed version matches your build:
xynginc --versionThis means you are missing the C compiler. Ensure you installed build-essential (Ubuntu) or "Development Tools" (CentOS).
This usually means libssl-dev or pkg-config is missing. Re-run the system dependencies installation step.
If you are building on x86_64 for an ARM target (or vice-versa), you will need to install the appropriate cross-compilation target via rustup (e.g., rustup target add aarch64-unknown-linux-gnu) and use a cross-linker. This is outside the scope of this basic guide.