-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[nanopb] Build error on x64-windows #44014
Comments
There are indeed double quotes, as shown below. However, no errors occurred on my machine and it installed successfully. config-x64-windows-out.log: May I ask, after you removed the double quotes in portfile.cmake, did the error disappear? |
Please note the remarks at the bottom of my report - this issue can only be reproduced if the path you install nanopb to contains a space. I see your path Please try the following instead:
|
Package: nanopb[core,generator]:[email protected]
Host Environment
vcpkg-scripts version: 6784dd4 2025-02-25 (82 minutes ago)
To Reproduce
NOTE: to reproduce the issue, this must be executed in a directory whose full path contains a space - see below for details
vcpkg install nanopb[generator]
Failure logs
D:\nanopb test\vcpkg\buildtrees\nanopb\config-x64-windows-dbg-CMakeConfigureLog.yaml.log
D:\nanopb test\vcpkg\buildtrees\nanopb\config-x64-windows-rel-CMakeConfigureLog.yaml.log
D:\nanopb test\vcpkg\buildtrees\nanopb\config-x64-windows-out.log
D:\nanopb test\vcpkg\buildtrees\nanopb\config-x64-windows-rel-CMakeCache.txt.log
D:\nanopb test\vcpkg\buildtrees\nanopb\config-x64-windows-dbg-CMakeCache.txt.log
Failure installing nanopb[generator] (regular nanopb is OK) on Windows 10/11 if vcpkg is invoked in a directory whose path contains a space. As far as I can work out, this is caused by the portfile incorrectly quoting the path passed to
vcpkg_cmake_configure
asnanopb_PROTOC_PATH
:vcpkg_cmake_configure
already takes care of quoting when invoking CMake, so you end up with double quoting which effectively unquotes the path:config-x64-windows-out.log:
Full steps to reproduce:
The text was updated successfully, but these errors were encountered: