CHANGE: include env vars for Win and Mac in the table instead

This commit is contained in:
GithubAnon0000 2025-11-02 17:55:39 +01:00
parent d040148b86
commit efb1b1a4bc

View file

@ -200,16 +200,15 @@ If ANKI_PROFILE_CODE is set, Python profiling data will be written on exit.
The steps to build the launcher vary slightly depending on your operating The steps to build the launcher vary slightly depending on your operating
system. First, you have to navigate to the appropriate folder: system. First, you have to navigate to the appropriate folder:
| Operating System | Path | | Operating System | Path | Env variables |
| ---------------- | ------------------ | | ---------------- | ------------------ | ------------- |
| Linux | ./qt/launcher/lin/ | | Linux | ./qt/launcher/lin/ | - |
| MacOS | ./qt/launcher/mac/ | | MacOS | ./qt/launcher/mac/ | `NODMG=1` |
| Windows | .\qt\launcher\win\ | | Windows | .\qt\launcher\win\ | `NOCOMP=1` |
If you are on Windows, you will now have to set `NOCOMP=1` to skip code signing If you are on Windows or MacOS, you will now have to set the environment
and compression. If you are on MacOS, you will have to use `NODMG=1` to skip the variables as outlined in the table above. `NOCOMP=1` skips code signing
slow bundling / code signing. If you are on linux, you won't have to set any and compression, whereas `NODMG=1` skips the slow bundling / code signing.
special environment variables.
Next, run the `build.sh` script (on Linux and MacOS) or the `build.bat` script Next, run the `build.sh` script (on Linux and MacOS) or the `build.bat` script
(on Windows). (on Windows).