Skip to content
qbittorrent-nox-static

Rules of Engagement

⭐ The rules of engagement are:

  1. Use Docker

    Section titled “Use Docker”
    • Docker is the recommended method for building with the script.
    • This avoids many potential issues and conflicts with the host system, especially with Qt.

  2. Use Alpine

    Section titled “Use Alpine”
    • Alpine is the main supported system; Debian is for testing and fallback.
    • You do not need to build on an older host to use these binaries there.

  3. Privileges

    Section titled “Privileges”
    • sudo or root privileges are not required to run the script.
    • They are only required to install core dependencies if they are missing.

  4. Additional flags and switches

    Section titled “Additional flags and switches”
    • Can add dependencies on demand that will need to be installed.
    • For example, -c for CMake and -cd for cache dependencies.
    • The script will require you to install these on demand.
    • Using .qbt_env or setting variables before running the script will handle this automatically.

  5. Passing no arguments

    Section titled “Passing no arguments”
    • qbt-nox-static.bash Recommended - will make no changes and instead provide information on what you need to do.
    • qbittorrent-nox-static.sh Legacy - will automatically install the required dependencies and configure the build environment.

  6. Nothing is built until…

    Section titled “Nothing is built until…”
    • You provide the all argument or a specific module name as a positional parameter to the script.
    • This applies to both qbt-nox-static.bash and qbittorrent-nox-static.sh.

  7. Use the help

    Section titled “Use the help”
    • Use bash ~/qbt.bash -h to see the help.
    • This applies to both qbt-nox-static.bash and qbittorrent-nox-static.sh.

  8. Fork the repo

    Section titled “Fork the repo”
    • Build on GitHub using GitHub Actions to create your own custom releases.
    • This is the easiest way to get custom builds for your needs.