Skip to content
build

win32: Use INI file for application configuration #185

Sign in to view logs

win32: Use INI file for application configuration

win32: Use INI file for application configuration #185

Triggered via push May 10, 2026 05:47
@benstonebenstone
pushed d561fdf
main
Status Success
Total duration 6m 18s
Artifacts 8

build.yml

on: push
Windows MSVC x86 Release
2m 27s
Windows MSVC x86 Release
Windows MSVC x64 Debug
1m 35s
Windows MSVC x64 Debug
Windows SDL MSVC x64 Debug
3m 54s
Windows SDL MSVC x64 Debug
Windows Clang x64 Release
6m 11s
Windows Clang x64 Release
Windows MSVC ARM64 Release
2m 24s
Windows MSVC ARM64 Release
Linux gcc x86_64 Debug
2m 46s
Linux gcc x86_64 Debug
Fit to window
Zoom out
Zoom in

Annotations

6 warnings and 4 notices
Windows MSVC x64 Debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows MSVC ARM64 Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows MSVC x86 Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Linux gcc x86_64 Debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows SDL MSVC x64 Debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows Clang x64 Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows MSVC x64 Debug
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows MSVC x86 Release
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows SDL MSVC x64 Debug
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Windows Clang x64 Release
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
3DMMEx Linux gcc x86_64 Debug
175 MB
sha256:f37fb5aff75d4aa549b95af67ef07753e00597944f692f8af765dfe114c025d5
3DMMEx Linux gcc x86_64 debug files
495 KB
sha256:773cca0f3c29dd690d999522c95e4fdde3f8eb3cb8027a8b553cec0278aa94d2
3DMMEx Windows ARM64
170 MB
sha256:ca85840506114ff96bc23c3162018d3c5864d1910517e60d6bfe007308388d9e
3DMMEx Windows ARM64 debug symbols
4.15 MB
sha256:d7b603f7b66fc8e86367bef70ab5e8dd00181c18f03e137f4c9310a115908915
3DMMEx Windows x64
170 MB
sha256:a1035ece49bcf207de08413143022600504b9e80c13e76b111881175d6fc4c37
3DMMEx Windows x64 debug symbols
4.95 MB
sha256:987ef8718cb339b9d82d7a0e66c402c65b679547af44e89153caec97ecacf0a5
3DMMEx Windows x86
170 MB
sha256:b22c9958212a7e303a966abd3ec6e058b726faaaeb543f889c0a9cf3ce648756
3DMMEx Windows x86 debug symbols
4.24 MB
sha256:f26b4b8cb97b9e93e7bd1e655971d2dc66bd50871c25d560b7d50887e53bc760