kvass/borscht
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kvass build system (BS) :trl:
28 commits 1 branch 0 tags 70 KiB
  • C 99.3%
  • Shell 0.7%
Find a file
Exact
jastahooman 9a1f5cb4eb (2.0c) NO MORE KVASS DOCS REPO LOLOLOL
2026-03-19 14:06:49 -05:00
borscht (2.0c) some crap crashes out if i dont remove the comments :( 2026-02-22 11:16:56 -06:00
configure.sh (1.3c) memory leak fix 2026-02-19 22:24:57 -06:00
kcfg.md (2.0c) NO MORE KVASS DOCS REPO LOLOLOL 2026-03-19 14:06:49 -05:00
LICENSE (1.0b) - FORGOT LICENSE OH NO OH NO NOH NOHNO HERI)POGKLERJHUWEJKFKHW^C 2026-02-19 17:09:45 -06:00
manual.md (2.0c) NO MORE KVASS DOCS REPO LOLOLOL 2026-03-19 14:06:49 -05:00
projcfg.cfg (1.3b) parser bug fixes, fix for load save function 2026-02-19 22:19:59 -06:00
readme.md (1.0b) some crap idk rewrote readme and disabled debug symbols 2026-02-19 17:30:47 -06:00

readme.md

Borscht

Copyright (c) jastahooman, 2026

Literally a build system, it is somewhat portable.

Dependencies

  • The user should have a C compiler (everyone compiling your project has one, believe me)
  • Access to the standard and POSIX libraries (unless it's a hobby OS, you'll be fine)
  • make (everyone compiling your project DEFINITELY at least has 'make')

Implementation Details

Note: using 'configure.sh' in the form it's provided in the repo is discouraged heavily! Please use it as a template!

  1. Copy the borscht directory and configure.sh into your program's build thing.
  2. The configure.sh can be changed, with the changes distributed. It is essentially public domain.
    • Note: Borscht can be used with another build system. It's main goal is to configure things.
    • Note 2: The projcfg.cfg file must be present in the Borscht running directory.
  3. Write a config file, instructions are in the kvass-docs repo, in specs/borscht.md
  4. Make sure it doesn't explode on you.
  5. Enjoy - thanks for using Borscht!