- Changed the output directory for Doxygen documentation to 'docs/' for better organization.
- Updated Visual Studio project generation command to use Python for enhanced vcpkg integration.
- Revised build instructions to clarify the use of vcpkg and added fallback mechanisms for CI/CD workflows.
- Updated subproject commit IDs for various libraries to ensure consistency across dependencies.
- Updated the condition for checking vcpkg availability in release workflows to enhance readability.
- Ensured consistent formatting across release-complex.yml, release-simplified.yml, and release.yml.
- Added a fallback mechanism for vcpkg setup to handle failures gracefully.
- Introduced environment variables to indicate vcpkg availability and switch to a minimal build configuration if vcpkg is not available.
- Updated CMake configuration to conditionally use vcpkg toolchain based on the availability flag.
- Changed the project file generation command from PowerShell to Python for better integration with vcpkg.
- Enhanced documentation to clarify automatic vcpkg dependency management for zlib, libpng, and SDL2.
- Added note that generated project files will remain in sync with CMake configuration.
- Deleted `YAZE.sln` and `YAZE.vcxproj` files as they are now generated automatically.
- Updated the Windows development guide to reflect changes in project file generation and vcpkg integration.
- Enhanced troubleshooting section with common issues related to dependencies and project setup.
- Modified setup script messages to clarify the new workflow for opening and building the project in Visual Studio.
- Updated the vcpkgGitCommitId to '2024.12.12' in release-complex.yml, release-simplified.yml, and release.yml for consistency.
- Added a new documentation file B4-release-workflows.md detailing the different release workflows, their purposes, features, and use cases.
- Updated index.md to include a link to the new release workflows documentation.
- Added a comment to indicate that the LoadSystemFonts function is intended for loading Linux system fonts into ImGui.
- Maintained the function for compatibility while ensuring it does not perform any operations on Linux, as system font loading is now handled by NFD (Native File Dialog).
- Updated the builtin-baseline in vcpkg.json to the latest version.
- Removed GLEW references from CMake files to avoid MSYS2 issues and streamline the build process.
- Adjusted include and link directories in z3ed.cmake to reflect the removal of GLEW.
- Removed Windows-specific font loading code to streamline the font loading process.
- Updated the LoadSystemFonts function to indicate that system font loading is now handled by NFD (Native File Dialog) for Linux.
- Maintained the function for compatibility while ensuring it does not perform any operations on Linux.
- Added additional Abseil flags modules to the CMake configuration for better support.
- Refactored Windows-specific font loading code to avoid namespace conflicts by using the `::` prefix for Windows API calls.
- Improved error handling and ensured proper memory management when retrieving font paths from the Windows registry.
- Introduced a new Python script, `generate-vs-projects-simple.py`, to create Visual Studio project files without complex CMake dependencies.
- The script generates both `.vcxproj` and `.sln` files, consolidating source and header files for the YAZE project.
- Updated the Windows development setup script to utilize the new generator, providing fallback to the original if the simple generator fails.
- Enhanced user instructions for building the project in Visual Studio.
- Transitioned from a function-based structure to a sequential approach, simplifying the script flow.
- Enhanced user feedback with clear status messages for each setup step, including checks for project directory, Visual Studio, Git, Python, and vcpkg.
- Improved error handling and instructions for missing dependencies, ensuring a smoother setup process.
- Streamlined the process for generating Visual Studio project files and testing builds, making it more user-friendly.
- Transitioned to a function-based approach, reducing complex conditional statements.
- Enhanced user feedback with a consistent messaging function for status updates.
- Modularized setup steps for checking project directory, Visual Studio, Git, Python, and vcpkg.
- Improved error handling and instructions for each setup step, ensuring a clearer user experience.
- Simplified the script structure by removing complex conditional statements.
- Enhanced output messages for each setup step, providing clearer guidance on the status of checks for project files, Visual Studio, Git, Python, and vcpkg.
- Improved error handling and user instructions for missing dependencies and setup steps.
- Streamlined the process for generating Visual Studio project files and testing builds, ensuring a more user-friendly experience.
- Refactored batch and PowerShell build scripts to streamline argument parsing and enhance error handling.
- Added support for cleaning build directories and improved feedback for missing dependencies.
- Updated project file generation logic to handle missing configuration files more gracefully.
- Introduced a new validation script to ensure the build environment is correctly set up before building.
- Removed obsolete setup scripts to simplify the repository structure.
- Enhanced Git and Python checks to ensure proper installation before proceeding with setup.
- Updated vcpkg cloning logic to verify Git availability and provide clearer error messages.
- Improved project file generation and build testing sections with additional user feedback and error handling.
- Removed obsolete PowerShell syntax test script to streamline the repository.
- Included GLEW, boost-system, boost-filesystem, and boost-thread as dependencies.
- Specified platform compatibility to exclude UWP for these libraries.
- Removed obsolete project entries from the solution file to streamline structure.
- Updated YAZE project configuration to enable vcpkg integration and multi-architecture support.
- Enhanced build scripts for Windows, including automated setup and testing processes.
- Added new documentation for Windows development setup and build instructions.
- Updated batch and PowerShell scripts to check for proper references to YAZE.vcxproj in the solution file.
- Added verification for project configurations, providing user feedback on their status.
- Improved messaging for error states to guide users in ensuring correct project setup.
- Updated batch and PowerShell scripts to improve the configuration process for Visual Studio projects.
- Enhanced user feedback by checking for existing solution files and verifying project references.
- Added help options in the PowerShell script to guide users on available parameters and usage examples.
- Improved messaging for success and error states to facilitate troubleshooting and user experience.
- Enhanced the installation process for build tools and dependencies using Chocolatey, with error handling for individual package installations.
- Added verification steps to confirm successful installation of CMake, Ninja, Git, and Python3.
- Updated environment setup to ensure a minimal build configuration and improved user feedback during the setup process.
- Revised build instructions to include comprehensive Windows support with automated setup scripts and Visual Studio integration.
- Added detailed sections for Windows development, including recommended setup scripts and manual options for vcpkg integration.
- Improved clarity on build commands and troubleshooting steps for CMake and Visual Studio issues.
- Introduced new scripts for testing CMake configuration and streamlined project generation processes.
- Added policies for submodule compatibility and suppressed deprecation warnings in CMakeLists.txt.
- Updated Visual Studio project generation scripts to include new CMake arguments for policy versions and thread handling.
- Introduced a new PowerShell script to test CMake configuration, ensuring successful setup and providing user feedback.
- Implemented checks for CMake in both batch and PowerShell scripts to ensure it is available before proceeding.
- Added logic to attempt installation of CMake via Chocolatey if not found, with appropriate user feedback.
- Enhanced user experience by providing instructions for manual installation if Chocolatey is not present.
- Included verification steps to confirm successful installation of CMake after the installation attempt.
- Introduced a new setup script for Windows development environment, automating the installation of essential tools like Git, Ninja, and Python 3, along with checks for Visual Studio.
- Restructured the solution file to better categorize projects, including new entries for Documentation, Scripts, and CMake.
- Updated project configurations to support multiple architectures (x86, x64, ARM64) and added new build types (RelWithDebInfo, MinSizeRel).
- Introduced new scripts for generating Visual Studio project files, enhancing the build process for Windows users.
- Removed obsolete project entries and streamlined the solution structure for clarity and maintainability.
- Added cleanup step for vcpkg state to prevent potential issues during builds.
- Implemented debugging step to provide detailed information if vcpkg setup fails.
- Introduced fallback mechanism to manually install dependencies if vcpkg fails.
- Updated CMake configuration to check vcpkg availability and adjust build settings accordingly.
- Added verification step for CMake configuration to ensure successful setup.
- Updated tag validation step to correctly output the validated tag name.
- Enhanced packaging commands to use Unix-style commands for better compatibility and error handling.
- Added verification step for build artifacts to ensure successful creation before packaging.
- Improved output messages for clarity during the build and packaging processes.
- Added multiple project entries for source, application, API, CLI, library, utilities, and testing components in the solution file.
- Included documentation and asset directories with relevant files for better organization and accessibility.
- Updated solution configurations to support ARM64 architecture alongside existing x64 and x86 configurations, ensuring comprehensive build support.
- Added separate steps for testing executable functionality on Windows, macOS, and Linux, improving clarity and organization.
- Streamlined the executable path determination for Windows and implemented similar logic for macOS and Linux.
- Enhanced error handling and output messages for better debugging during the testing process.
- Improved buffer size calculations for font name and data to enhance safety and prevent overflow.
- Streamlined the maximum font loading limit to ensure efficient font management while maintaining clarity in the code.
- Added architecture detection in CMakeLists.txt for Windows, defining appropriate compile flags for ARM64, x64, and x86 platforms.
- Updated yaze.vcxproj to include Debug and Release configurations for ARM64, ensuring proper setup for ARM64 builds.
- Modified GitHub Actions workflow to support packaging for Windows ARM64, creating artifacts for both x64 and ARM64 builds.
- Added `_SILENCE_ALL_CXX23_DEPRECATION_WARNINGS` definition to suppress all C++23 deprecation warnings in CMakeLists.txt for both MSVC and GCC/Clang.
- Updated `yaze.vcxproj` to remove unnecessary `absl::numeric` from AdditionalLibraryDirectories, streamlining library paths.
- Modified `absl.cmake` to conditionally include `absl::int128` only on non-Windows platforms, avoiding C++23 deprecation issues and improving cross-platform compatibility.
- Updated packaging commands in the release workflow to use Windows-compatible commands for copying files.
- Enhanced error handling for missing files and directories during the packaging process.
- Improved formatting of the Info.plist generation for better readability.
- Adjusted the shell used in the packaging step to be platform-specific, ensuring compatibility across different operating systems.
- Updated font configuration to include proper ImFontConfig initialization for each font entry in the font registry.
- Enhanced code clarity by adding comments to describe the initialization process.
- Updated CMakeLists.txt to silence C++23 deprecation warnings and added definitions for intrinsic int128 support.
- Modified GitHub Actions workflow to handle missing asset directories gracefully and ensure correct versioning in Info.plist.
- Refactored string handling in multiple source files to use std::memcpy for safer string copying, preventing potential buffer overflows.
- Improved font loading logic and ensured consistent handling of theme properties in the editor.
- Added 'absl::numeric' to the AdditionalLibraryDirectories in yaze.vcxproj for enhanced functionality.
- Refactored string handling in multiple source files to use std::strncpy for safer string copying and prevent buffer overflows.
- Cleaned up unnecessary whitespace and improved code readability across various files.
- Removed unused includes and improved code readability by renaming variables for clarity.
- Updated font size constants to use uppercase 'F' for consistency.
- Implemented helper functions for better handling of font paths and normalization.
- Enhanced the LoadSystemFonts function to load essential Windows fonts and added error handling for font loading failures.
- Streamlined the registry font loading process to ensure safer and more efficient font management.
- Updated CMakeLists.txt to include additional MSVC compiler options for better compatibility and performance, such as support for large object files and UTF-8 encoding.
- Modified absl.cmake to add support for absl::int128.
- Refactored file dialog implementation in file_dialog.cc to utilize a feature flag for native file dialog support, improving cross-platform compatibility and maintainability. Added placeholder implementations for CI/CD environments.
- Created a new document detailing the installation and configuration of the `x64-windows` triplet for building YAZE on Windows.
- Included multiple methods for triplet installation, common issues and solutions, and alternative triplet options.
- Provided verification steps and instructions for building YAZE using the configured triplet, enhancing clarity for developers.
