- Added new session summary documentation for the z3ed agent implementation on October 2, 2025, detailing achievements, infrastructure, and usage. - Created evening session summary documenting the resolution of the ImGuiTestEngine runtime issue and preparation for E2E validation. - Updated the E2E test harness script to reflect changes in the test commands, including menu item interactions and improved error handling. - Modified imgui_test_harness_service.cc to implement an async test queue pattern, improving test lifecycle management and error reporting. - Enhanced documentation for runtime fixes and testing procedures, ensuring comprehensive coverage of changes made.
yaze Build Scripts
This directory contains build and setup scripts for YAZE development on different platforms.
Windows Scripts
vcpkg Setup (Optional)
setup-vcpkg-windows.ps1- Setup vcpkg for SDL2 dependency (PowerShell)setup-vcpkg-windows.bat- Setup vcpkg for SDL2 dependency (Batch)
Note: vcpkg is optional. YAZE uses bundled dependencies by default.
Windows Build Workflow
Recommended: Visual Studio CMake Mode
YAZE uses Visual Studio's native CMake support - no project generation needed.
- Install Visual Studio 2022 with "Desktop development with C++" workload
- Open Visual Studio 2022
- File → Open → Folder
- Navigate to yaze directory
- Select configuration (Debug/Release) from toolbar
- Press F5 to build and run
Command Line Build
# Standard CMake workflow
cmake -B build -DCMAKE_BUILD_TYPE=Debug
cmake --build build --config Debug
# Run the application
.\build\bin\Debug\yaze.exe
Compiler Notes
The CMake configuration is designed to work with MSVC (Visual Studio's compiler). The build system includes automatic workarounds for C++23 compatibility:
- Abseil int128 is automatically excluded on Windows
- C++23 deprecation warnings are properly silenced
- Platform-specific definitions are handled automatically
Quick Start (Windows)
Option 1: Visual Studio (Recommended)
- Open Visual Studio 2022
- File → Open → Folder
- Navigate to yaze directory
- Select configuration (Debug/Release)
- Press F5 to build and run
Option 2: Command Line
# Standard CMake build
cmake -B build -DCMAKE_BUILD_TYPE=Debug
cmake --build build --config Debug
Option 3: With vcpkg (Optional)
# Setup vcpkg for SDL2
.\scripts\setup-vcpkg-windows.ps1
# Then build normally in Visual Studio or command line
Troubleshooting
Common Issues
-
PowerShell Execution Policy
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser -
Visual Studio Not Detecting CMakeLists.txt
- Ensure you opened the folder (not a solution file)
- Check that CMakeLists.txt exists in the root directory
- Try: File → Close Folder, then File → Open → Folder
-
vcpkg Issues (if using vcpkg)
- Run
.\scripts\setup-vcpkg-windows.ps1to reinstall - Check internet connection for dependency downloads
- Note: vcpkg is optional; bundled dependencies work by default
- Run
-
CMake Configuration Errors
- Delete the
build/directory - Close and reopen the folder in Visual Studio
- Or run:
cmake -B build -DCMAKE_BUILD_TYPE=Debug
- Delete the
-
Missing Git Submodules
git submodule update --init --recursive
Getting Help
- Check the Build Instructions
- Review CMake output for specific error messages
- Ensure all prerequisites are installed (Visual Studio 2022 with C++ workload)
Other Scripts
create_release.sh- Create GitHub releases (Linux/macOS)extract_changelog.py- Extract changelog for releasesquality_check.sh- Code quality checks (Linux/macOS)create-macos-bundle.sh- Create macOS application bundle for releases