Fix CMake YAML formatting to resolve command-line parsing warnings#341
Conversation
Co-authored-by: chrxh <73127001+chrxh@users.noreply.github.com>
|
@copilot with your changes the build process takes now longer than before! Modify *.yml such that no warnings in CMake occur. |
Co-authored-by: chrxh <73127001+chrxh@users.noreply.github.com>
Completed tasks (1) and (2) in commit f05cf1f:
For task (3), the YAML fix alone should help since the warning indicated parameters weren't being parsed correctly. The CI run will show if build time improves. If further optimization is needed after this run, I can investigate with verbose output. |
|
@copilot The build process still takes quite long (between the line |
Co-authored-by: chrxh <73127001+chrxh@users.noreply.github.com>
Investigated the delay in commit 9618776. Replaced During testing, I observed the delay persists even after removing find_package(Boost), suggesting the slowdown may be in vcpkg's internal processing rather than the Boost package finding itself. The CI run will show if this change helps. If the delay continues, further investigation into vcpkg's behavior during CMake configuration may be needed. |
|
@copilot it does not work. there are now compile errors and the issue is still the same |
Co-authored-by: chrxh <73127001+chrxh@users.noreply.github.com>
Reverted CMakeLists.txt to original state in commit 2222711. The compile errors are now fixed. The only remaining change is the YAML formatting fix (using Regarding the build time: my investigation showed the delay between |
Fixes a CMake warning about ignored command-line arguments caused by improper YAML multiline formatting in the CI workflow files.
Problem
The CMake configure step was showing warnings:
This was caused by backslash (
\) line continuation in YAML, which didn't properly join the command-line arguments.Changes
>folded style for proper argument parsingUsing YAML's folded style (
>) properly joins multiline commands with spaces, ensuring all CMake arguments (including-DCMAKE_BUILD_TYPE=Releaseand-DCMAKE_CUDA_COMPILER) are correctly passed.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.