ps
/
4coder
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2,263 Commits 2 Branches 0 Tags 52 MiB
C++ 71.3%
C 27.8%
Objective-C++ 0.4%
Roff 0.3%
Go to file
Khoa Vo a99c36fd49
Update README.md build instruction 
Avoid confusion when someone only runs the build script and get errors about missing fonts.
 		2023-12-17 16:58:10 +02:00
code Remove scripts to update Itch.io page 2023-02-04 15:21:00 +00:00
non-source Add 'non-source/' from commit 'fd5f072a79d81b9f15aa183a65b6384de8344d6b' 2022-11-18 14:05:59 +00:00
.gitignore Correct build for new structure 2022-11-18 16:43:00 +00:00
README.md Update README.md build instruction 2023-12-17 16:58:10 +02:00

README.md

4Coder Community

Welcome to the 4coder community repository.

Building

Windows

  1. Setup the MSVC toolchain in your environment, this can be done with the code/custom/bin/setup_cl_x64.bat script
  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, 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

Linux

tested on Ubuntu 22.04:

  1. Get required libraries (apt names):

    • $ sudo apt install build-essential libx11-dev libxfixes-dev libglx-dev mesa-common-dev libasound2-dev libfreetype-dev libfontconfig-dev

  2. Use the package-linux.sh script to build and package an application

    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, 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.