You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It handles a lot of the nuanced complexity around building various different dependencies on two different host platforms, towards the same outcome, whilst targeting these architectures:
15
15
16
16
<Detailssummary=" target architectures">
17
-
`aarch64` - `armel`- `armhf`- `armv7`
17
+
`armel``armhf``armv7``aarch64`
18
18
19
-
`x86` - `x86_64`
19
+
`x86_64``x86`
20
20
21
-
`powerpc` - `ppc64el`
21
+
`s390x`
22
22
23
-
`mips` - `mipsel` - `mips64` - `mips64el`
23
+
`powerpc``ppc64el`
24
+
25
+
`mips``mipsel``mips64``mips64el`
26
+
27
+
`riscv64`
24
28
</Details>
25
29
30
+
26
31
⭐ On supported host build platforms the `qbittorrent-nox-static.sh` will perform these three main tasks via simple prompt:
We do not support a non docker build environment. If you are not using docker, you are on your own.
10
+
:::
11
+
12
+
:::tip[Github Actions]
13
+
If you cannot or don't want to use docker, you can use the [Github Actions](/qbittorrent-nox-static/github-actions) to build the project by forking the repository.
14
+
:::
15
+
16
+
## Bootstrapping the container
9
17
10
18
<Tabs>
11
19
<TabItemvalue="Notes"label="Notes">
12
20
13
21
Some notes on the dockers method:
14
22
15
-
- We use a subdirectory, not your `$HOME` directory, to avoid `.bashrc` and `.profile` conflicts.
23
+
- The script itself install thes necessary dependencies so there is no docker file needed.
24
+
- We use a subdirectory `qbt`, not your `$HOME` directory, to avoid `.bashrc` and `.profile` conflicts.
16
25
- A subdirectory is automatically created, named `qbt` by the use of `-v $HOME/qbt:/root`
17
26
- The default path will be `HOME/qbt` outside the docker container and `/root/qbt` inside it.
18
27
- We use `-e "LANG=en_GB.UTF-8"` with Debian based images to avoid some errors.
19
28
29
+
:::tip[env file]
30
+
There are multiple ways to pass an env file when using Docker.
31
+
32
+
- You can use the `--env-file` switch when creating the docker and provide a file with your [envs](/qbittorrent-nox-static/build-help#env-settings).
33
+
- If a `.qbt_env` file is found in the same directory as the script, it will be used automatically.
34
+
- Using ENV in a dockerfile is also possible.
35
+
:::
36
+
20
37
</TabItem>
21
38
<TabItemvalue="Debian Linux"label="Debian">
22
39
@@ -27,32 +44,32 @@ You use `debian:bullseye` `debian:bookworm` `debian:latest` or a supported tag
If you need to install the dependencies and you have `sudo` privileges then do this:
107
-
108
-
:::caution
109
-
This only needs to be done once, as root, to install the dependencies. Using certain enviroment variables or switches can add dependencies, like `-c` for cmake.
110
-
111
-
You may need to escalate your privileges again.
112
-
:::
113
-
114
-
```bash
115
-
sudo bash ~/qbittorrent-nox-static.sh
116
-
```
117
-
118
-
## Docker via SSH
119
-
120
-
Some notes on the dockers method:
121
-
122
-
- We use a subdirectory, not your `$HOME` directory, to avoid `.bashrc` and `.profile` conflicts.
123
-
- A subdirectory is automatically created, named `qbt` by the use of `-v $HOME/qbt:/root`
124
-
- The finale default path will be `HOME/qbt` outside the docker container and `/root/qbt` inside it.
125
-
126
-
:::tip
127
-
build envs can be passed to the docker using `-e` . Such as `-e qbt_cross_name=aarch64`
128
-
:::
129
-
130
-
<Tabs>
131
-
<TabItemlabel="Debian">
132
-
133
-
:::tip
134
-
You use `debian:bullseye``debian:bookworm``debian:latest`
0 commit comments