How lompy/otushw works
Project type and purpose
• This repository (“otushw”) is a collection of C++ homework exercises organized by lesson number.
• There is no “live” multi-tier application or service: each subdirectory under cpp-basic (e.g., 02, 03) contains standalone example programs and corresponding CMake build files.
File structure
• Top-level:
• .gitignore
• README.md (project overview)
• cpp-basic/ (container for course exercises)
• Under cpp-basic:
• 02/ and 03/ directories, each with
– CMakeLists.txt (build configuration)
– .cpp and .hpp files (source and header files)
• There are no external services, databases, or tests folders—just code examples and CMake build rules.
README for additional insights
• The README simply states this is an Otus homework repository, with each course occupying its own folder.
• No further architectural guidance or external dependencies are documented.
a. Main components
1. Source Code Modules
– Example programs (example.cpp, hello_world.cpp, etc.)
– Header files (.hpp)
2. Build System
– CMake (CMakeLists.txt)
3. Build Targets / Executables
– Generated binaries for each exercise
4. Developer Environment (implicit)
– Compiler (e.g., GCC/Clang)
– CMake generator (Makefiles, Ninja, etc.)
b. Relationships and interactions
• CMakeLists.txt reads the source and header files to configure build targets.
• CMake invokes the local compiler toolchain to produce executables.
• Developers run the binaries to verify behavior.
c. Architectural patterns / design principles
• Modular organization by lesson number.
• Clear separation of source (.cpp) and interface (.hpp).
• Use of a cross-platform build system (CMake).
d. Key technologies / frameworks
• C++17 (or whichever standard is specified in CMakeLists.txt)
• CMake (build orchestration)
Detailed breakdown
• Top layer: “otushw” root (label it)
• Underneath: two parallel lanes, one for cpp-basic/02, one for cpp-basic/03
• Inside each lane:
• Central build flow:
• “CMake” → “Build System” → “Compiler/Linker” → “Executable(s)”