Stub for code generation. The actual workflow lives in
../docs/codegen.md; this folder is where
generated sources and toolbox-specific configurations are kept.
codegen/
├── matlab/
│ ├── codercfg.m.example # example MATLAB Coder configuration
│ ├── codercfg.m # (you create this from the example)
│ ├── entries.txt # list of entry points for build_codegen.m
│ └── src/ # generated .cpp/.hpp
└── simulink/
├── entries.txt # list of models for build_codegen.m
└── <model>/ # generated .cpp/.hpp per model
scripts/build_codegen.m reads the two
entries.txt manifests and runs MATLAB Coder / slbuild for each
entry. It exits non-zero on any failure so it can be wired into CI
later without code changes.
# Linux / macOS / WSL / Git Bash
./scripts/build_codegen.sh
# Native Windows PowerShell
.\scripts\build_codegen.ps1
# Interactive MATLAB
>> setup
>> build_codegen*.cpp,*.hpp,*.hgenerated by MATLAB/Simulink Coder.codercfg.mconfigurations (renamed from.exampleonce adopted).entries.txtonce it lists real entry points.- Hand-written CMakeLists.txt / Makefiles under
codegen/<tool>/.
- Object files, shared/static libraries, executables.
slprj/,slexec/,slbuild/,build/,cmake-build-*/.*.slxc,*.slx.r20*.