Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX(cmake): Don't set WORKING_DIRECTORY for ExternalProject_Add() #6640

Conversation

davidebeatrici
Copy link
Member

This is a workaround for a bug that appeared in a recent version of CMake.

WORKING_DIRECTORY prepends the specified path to a list instead of using it directly, resulting in:

cd /D D:\a\1\b\overlay\overlay_xcompile-prefix;D:\a\1\b\overlay\overlay_xcompile-prefix\src\overlay_xcompile-build

For reference, this causes the build to fail on Windows with the following error:

"The filename, directory name, or volume label syntax is incorrect."

This commit simply removes the parameter from the ExternalProject_Add() call, since the default working directory is perfectly fine.

This is a workaround for a bug that appeared in a recent version of CMake.

WORKING_DIRECTORY prepends the specified path to a list instead of using it directly, resulting in:

cd /D D:\a\1\b\overlay\overlay_xcompile-prefix;D:\a\1\b\overlay\overlay_xcompile-prefix\src\overlay_xcompile-build

For reference, this causes the build to fail on Windows with the following error:

"The filename, directory name, or volume label syntax is incorrect."

This commit simply removes the parameter from the ExternalProject_Add() call, since the default working directory is perfectly fine.
@davidebeatrici davidebeatrici added windows build Everything related to compiling/building the code labels Nov 28, 2024
…endencies

Looks like targets are now built concurrently, which results in the installer failing to find the G15 and x64 overlay helpers.

This commit marks the G15 and overlay targets as dependencies of the client, when they're enabled.

As a bonus, plugins are now tied to their own dedicated target rather than the client's.
This is required because the client's subdirectory is now included later on.
@davidebeatrici davidebeatrici force-pushed the cmake-externalproject-no-working-directory branch from 6f93ae3 to 2a0683d Compare November 29, 2024 04:18
@Hartmnt Hartmnt merged commit 9ee2f4b into mumble-voip:master Nov 29, 2024
15 checks passed
@Krzmbrzl
Copy link
Member

💔 All backports failed

Status Branch Result
1.5.x Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

backport --pr 6640

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@Hartmnt
Copy link
Member

Hartmnt commented Nov 29, 2024

This is HartBot beep boop beep. I have successfully and automatically backported this PR as #6641
beep beep ✔️ 1.5.x

@davidebeatrici davidebeatrici deleted the cmake-externalproject-no-working-directory branch November 29, 2024 12:20
Hartmnt added a commit that referenced this pull request Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport-to-1.5.x build Everything related to compiling/building the code windows
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants