How ayxg/ssgc works
Project type and purpose
• This is a C++ “monorepo” packaging a full C& language environment: a compiler & VM, an IDE/CLI front‐end, extended standard libraries, meta‐template utilities, and a minimal testing framework.
• The goal is to allow you to build and deploy C& programs from command line or GUI, embed the IDE in a browser (future), and scale safely with metaprogramming.
File structure
• Top‐level CMakeLists.txt and CMakePresets.json orchestrate all subprojects in projects/.
• Under projects/ you have:
• cide_box – the IDE / command‐line front end (CIDE executable + library)
• cnd_box – the C& Official Compiler & Virtual Machine (CAOCO)
• cxxx_box – C++ Extended Standard Library (CXX)
• mta_box – Meta Template Archive (MTA)
• minitest_box – Minimal C++ unit‐test framework (MINT)
• plus several supporting/demo libraries (caf_box, cgui_box, ssgmono_box, wpl_box, etc.)
• Each subproject follows the pattern: inc/ for headers, src/ for implementation, test/ or ut/ for tests, and uses its own CMakeLists.txt.
Key insights from the README
• It explicitly names the five main modules (CIDE, CAOCO, CXX, MTA, MINT) and their layering:
MTA → CXX → CAOCO → CIDE
(and MINT hooking into all for tests)
• External dependencies: ImGui‐SFML (temporary), Vulkan (future), browsers for embedding.
Main components and their relationships
• MTA: Meta Template Archive (pure header library)
• CXX: C++ Extended Standard Library (static library)
• CAOCO: Compiler + VM (library + CLI cnd executable)
• CIDE: IDE / CLI front end (GUI & CLI executables + cide library)
• MINT: Unit‐test harness (library + runner)
• External: ImGui‐SFML, SFML, CMake, VulkanAPI (future), Browser Embed
b. Dependencies & data flow
• MTA → CAOCO (compiler uses meta utilities)
• CXX → CAOCO (compiler may compile against extended std)
• CAOCO → CIDE (IDE invokes compiler API or spawns compiler process)
• ImGui‐SFML → CIDE (GUI layer)
• MINT → All subprojects (unit tests link their code into MINT runner)
c. Architectural patterns
• Monorepo with CMake multi‐project orchestration
• Layered libraries (each layer only depends on lower‐level layers)
• Plugin‐style front end (CIDE loads or calls compiler as a library or external tool)
• MVC‐like separation in CIDE: UI (ImGui widgets) vs Backend (build/compile tasks)
d. Major technologies & frameworks
• CMake for build and dependency management
• ImGui‐SFML for temporary GUI in CIDE
• SFML for windowing / input
• VulkanAPI / Browser (future embedding target)
• Standard C++17/20 and custom meta‐template utilities (MTA)
Final touches
• If space permits, show internal submodules: inside CAOCO, separate “Lexer/Parser”, “IR Generator”, “Codegen”, “Virtual Machine”.
• In CIDE, show “UI Module (ImGui)”, “Build Manager”, “Project Model (JSON)”, “Launcher” as subcomponents.