ps
/
4coder
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md build instruction 

Avoid confusion when someone only runs the build script and get errors about missing fonts.
This commit is contained in:
Khoa Vo 2023-12-17 16:58:10 +02:00 committed by GitHub
parent cbeb374b18
commit a99c36fd49
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -9,7 +9,7 @@ Welcome to the 4coder community repository.
2. call the `package.bat` script from the code directory
1. `$ cd 4cc\code`
2. `.\bin\package.bat`
3. You can also use the `build.bat` script if you want just build the binaries, this does not copy the default config, fonts and bindings
3. You can also use the `build.bat` script if you want just build the binaries, this does not copy the default config, fonts and bindings, so you'll still still need to call the packaging script first, copy the files under `current_dist...` over to the `build` directory, then run the build script
1. `$ cd 4cc\code`
2. `$ .\bin\build.bat`
@ -22,9 +22,9 @@ Welcome to the 4coder community repository.
1. `$ cd 4cc/code`
2. `$ ./bin/package-linux.sh`
3. You can also use the `build-linux.sh` script if you want just build the binaries, this does not copy the default config, fonts and bindings
3. You can also use the `build-linux.sh` script if you want just build the binaries, same as on Windows
1. `$ cd 4cc/code`
2. `$ ./bin/build-linux.sh`
## Mac (Untested)
1. The steps should be the same as linux but replace the `*-linux.sh` with their `*-mac.sh` equivalents.
1. The steps should be the same as linux but replace the `*-linux.sh` with their `*-mac.sh` equivalents.