└── README.md


/README.md:
--------------------------------------------------------------------------------
 1 | # tccbin
 2 | 
 3 | This repository contains prebuilt executables for TCC, for different operating systems.
 4 | 
 5 | PRs should be done to the corresponding branches. If a branch for your
 6 | target triplet is not already created, please make an issue about it.
 7 | 
 8 | Note: *Do not make PRs to the `master` branch. They will be closed.*
 9 | 
10 | # TCC
11 | TCC can be obtained from https://repo.or.cz/tinycc.git (follow the instructions there).
12 | 
13 | Note: you have to compile it with `--config-backtrace=yes` and `--config-bcheck=yes`,
14 | for V to work without additional V flags. The reason for that, is the V's builtin module
15 | has calls to tcc_backtrace() for panics, when tcc is used, and tcc's bounds checking is
16 | useful as a debugging aid for prototyping and debug builds.
17 | 
18 | If those flags do not work for you, your users will have to pass: 
19 | `-d no_backtrace` and `-d no_segfault_handler` while compiling
20 | their programs with your prebuilt tcc, which is not very convenient.
21 | 
22 | You also need to ensure that the values you pass to --prefix and
23 | --bindir, during tcc's configuration stage, point to thirdparty/tcc .
24 | 
25 | The rest of the options can vary depending on the platform.
26 | 
27 | # Add a Build script for easier future reproductions with newer version of TCC
28 | You can look/copy [build.sh](https://github.com/vlang/tccbin/blob/thirdparty-linux-amd64/build.sh),
29 | and customize it for your new build. Please include a copy of the customized build script with your PR.
30 | 


--------------------------------------------------------------------------------