ci: keep workflow Qt-only and bump to 6.6.1 - #65
Open
edmc25 wants to merge 12 commits into
Open
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Set CMAKE_BUILD_TYPE=Debug for both Linux and Windows builds, deploy debug Qt DLLs via windeployqt --debug, and pin aqtversion to 3.3.0 in the Windows jurplel/install-qt-action step to match the Linux job. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The aqt win64_mingw Qt 6.6.1 kit only ships Release Qt binaries (no debug platform plugin), so windeployqt --debug failed with "Unable to find the platform plugin" once XilEnvGui.exe was built with debug info. Force --release deployment instead; MinGW has no debug/release CRT ABI split, so a Debug app linking Release Qt DLLs is safe. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Local gdb run of the CI-built XilEnvGui.exe hit a heap corruption (RtlFreeHeap invalid address) that the debugger only caught at the free() site, not the actual corrupting write. Compile the Windows Debug build with -fsanitize=address so the CI test run (and any locally downloaded artifact, given a matching libasan runtime) reports the exact location of the memory bug instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The win32-thread-model niXman MinGW-w64 14.2.0 build doesn't ship
libasan, so the -fsanitize=address Debug build failed to link
("cannot find -lasan"). AddressSanitizer requires the posix-thread
variant, so switch the download to
x86_64-14.2.0-release-posix-seh-ucrt-rt_v12-rev2.7z.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The app was compiled with niXman MinGW-w64 GCC 14.2.0 (UCRT), while the Qt 6.6.1 win64_mingw binaries from aqt are prebuilt with GCC 11.2.0 (posix, SEH, msvcrt) -- confirmed via the aqt install log's "MinGW-w64-x86_64-11.2.0-release-posix-seh-rt_v9-rev1-runtime.7z". Mixing UCRT and msvcrt across the app/Qt DLL boundary is a known cause of heap corruption (separate CRT heaps), matching the RtlFreeHeap crash seen when debugging XilEnvGui.exe locally. Switch to the matching x86_64-11.2.0-release-posix-seh-rt_v9-rev1 toolchain. Also revert the -fsanitize=address flags added earlier for the ASan attempt -- these niXman builds don't ship libasan, so the build couldn't link. Dropping that approach in favor of the toolchain fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Download and build Qt 6.6.1 (qtbase) with SVG submodule from source - Use Release build only for faster CI - Set up MinGW and Qt paths properly for CMake configuration - Pass explicit Qt6_DIR to OpenXilEnv CMake build Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Remove incorrect qtsvg submodule initialization from qtbase - Clone qtsvg repository separately at v6.1.1 - Configure, build, and install qtsvg against Qt 6.6.1 prefix Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Upgrade niXman MinGW from 11.2.0 to 14.2.0-rt_v12-rev2 (UCRT) to match recommended toolchain in WINDOWS_DEPENDENCIES.md - Remove explicit CMAKE_BUILD_TYPE=Debug from Linux build - Add --parallel to Windows OpenXilEnv cmake build step Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
windres.exe fails to handle the space in 'C:\Program Files\PostgreSQL\...' path. Disable the psql feature since OpenXilEnv does not need it. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Replace qtsvg v6.1.1 with v6.6.1 in Windows workflow - Update qtsvg build step names and source path accordingly - Fix configure failure caused by Qt module/base version mismatch Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.