Open k0zmo opened 2 weeks ago
what about binary caching? if I do the artifacts on a proper pc and reuse in one with spaces in path, your proposed solution does not intercept the problem
There's no problem with consuming the port, only with building it. You can use classic mode: vcpkg install ffmpeg
and consume the port from the path with spaces just fine. The problem is only triggered when you need to build ffmpeg.
Is your feature request related to a problem? Please describe.
The
ffmpeg
port currently verifies that the build tree path does not contain spaces. However, in manifest mode, it fails to check if theCURRENT_HOST_INSTALLED_DIR
contains spaces. When the project is located in a path with spaces, the build fails with an unclear error message, making it difficult for users to diagnose the issue.Proposed solution
To provide a clearer error message and prevent build failures, extend the existing path validation in
portfile.cmake
to also check theCURRENT_HOST_INSTALLED_DIR
. This can be done by modifying theportfile.cmake
as follows:Describe alternatives you've considered
No response
Additional context