ed/SectrPrototype
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Modifiaitons to build script

Browse Source 
I only keep the generated code_compiler_staged dir around if there are errors compiling
This commit is contained in:
Edward R. Gonzalez
2024-05-16 13:35:03 -04:00
parent 40ffed9538
commit 0527a033c8
3 changed files with 27 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Readme.md
View File

@ -22,17 +22,17 @@ The dependencies are:
* Odin repo's base, core, and vendor(raylib) libaries
* An ini parser
* backtrace
* Powershell (if you want to use my build scripts)
The client(sectr) module's organization is relatively flat due to the nature of odin's compiler, not allowing for cyclic dependencies across modules, and modules can only be in one directory.
This makes it difficult to unflatten, not something organic todo in a prototype...
I have the codebase by default in a non-idomatic layout that I stage to the compiler beforehand. There is a script(`scripts/gen_staged_compiler_codebase.ps1`) that stages a the idiomatic format of the codebase for the compiler to digest when `scripts/build.ps1` is run.
Even so the notable groups are:
Major 'codebase modules':
* API : Provides the overarching interface of the app's general behavior. Host uses this to provide the client its necessary data and exection env.
* Has the following definitions: startup, shutdown, reload, tick, clean_frame
* Engine : Main loop, logging, client interface for host, etc
* Has the following definitions: startup, shutdown, reload, tick, clean_frame (which host hooks up to when managing the client dll)
* Env : Core Memory & State definition + orchestration
* Font Provider : Manages fonts.
* When loading fonts, the provider currently uses raylib to generate bitmap glyth sheets for a range of font sizes at once.