How mrlion73/morpion works
Project type and purpose
• This is a small C++ desktop GUI application (a “Morpion” or Tic-Tac-Toe clone), primarily used as a learning exercise for CMake, CPack, and GitHub workflows.
File structure
• Top-level:
• README.md, LICENSE, .gitignore – documentation and metadata
• src/ – all source code and build scripts
• Inside src/:
• CMakeLists.txt – build configuration
• main.cpp – application entry point
• mainwindow.h/.cpp – GUI window class (View + Controller logic)
• No separate “model” directory, so game logic likely lives in mainwindow.cpp or main.cpp.
README for additional insights
• Build uses CMake (MinGW Makefiles)
• Packaging uses CPack, requires a “deploy” folder with DLLs
• No mention of external services or databases – it’s purely a local desktop app
Main components
a. Source & Build Layer
– CMakeLists.txt (generator of build system)
– Build tool: cmake / mingw-make
– CPack (packaging tool)
b. Runtime Components
– Executable (“Morpion.exe”)
– GUI Layer (MainWindow class + Qt or WinAPI underneath)
– External DLL dependencies (listed in deploy folder)
c. Developer Workflow
– GitHub repo (push/pull triggers CI, releases)
– Release artifacts (ZIP with deploy folder)
Relationships & data flow
• CMakeLists.txt feeds into the build tool → produces the executable and resource object files.
• CPack reads build outputs + “deploy” folder → packages final installer/ZIP.
• The executable dynamically loads required DLLs shipped alongside.
Architectural patterns & tech stack
• Technology: C++17 (or similar), CMake, CPack, MinGW, Windows resource compiler (.rc/.res)
• Pattern: Single-binary desktop app, combining View (mainwindow UI) and Controller (game rules) in one module.
• No external services, no database.