How jaskejaske1/c-fundamentals works
Project Type and Purpose
• This is an educational/portfolio repository containing C exercises for a “C Programming Fundamentals” course.
• It is not a multi-tier web app or microservice; rather, it’s a monorepo of Visual Studio solutions and matching Linux C source trees, plus CI build scripts.
File Structure Analysis
• Top-level:
• .github/workflows/ → GitHub Actions CI configurations (windows build, linux build, msbuild).
• C_Fundamentals_Exercises/ → Windows Visual Studio solution (.sln) with many C projects (.vcxproj).
• C_Fundamentals_Exercises_linux/ → Mirror of exercises as raw .c files for Linux.
• Les_<date>/ and Lessen_week_<date>/ → Additional dated lesson solutions (.sln + projects).
• LightingProgram/ → A separate solution (possibly demo or test).
• README.md, .gitignore, export scripts, etc.
• Pattern: monorepo segmented by course sections, with per-exercise project folders.
README Insights
• Confirms it’s portfolio and study material.
• Mentions no license (usage constraints).
• Notes that each Visual Studio solution maps to a course part.
Main Components
a. Version Control System (VCS)
• Git on GitHub (monorepo)
b. Continuous Integration (CI) Layer
• GitHub Actions workflows:
• Windows build (msbuild.yml)
• Linux build (build.yml)
c. Code Modules
• Solutions (.sln) as containers:
• C_Fundamentals_Exercises
• C_Fundamentals_Exercises_linux
• Les_<date>, LightingProgram, etc.
• Inside each solution: multiple C project folders with .vcxproj or .c files.
d. Build Toolchains
• Windows: MSBuild / Visual Studio compiler
• Linux: gcc (or make via CI script)
e. Artifacts
• Executables per exercise
f. Supporting Scripts
• Export-OefeningenLinux.ps1
Relationships and Data Flow
• Developer → GitHub Repo : push commits.
• GitHub Actions triggers on push/PR:
• Windows CI job checks out code → runs MSBuild on each solution → publishes success/failure.
• Linux CI job checks out code → compiles .c files in C_Fundamentals_Exercises_linux → publishes results.
• Artifacts (optional) could be stored or simply tested.
Architectural Patterns and Principles
• Monorepo: single repository hosting all course content.
• Separation by Platform: Windows VS solutions vs raw Linux C source.
• Modularity: each exercise isolated in its own project/folder.
• CI as Code: workflows defined declaratively in .github/workflows.
2. Inside, place sub-containers:
– “C Fundamentals VS Solutions”
– “C Fundamentals Linux Exercises”
– “Lessons by Date”
– “LightingProgram”
5. Finally, from build tools to “Compiled Binaries / Test Results.”