Can't export prefabs: Your vcpkg 'installed' tree is corrupted. #35538
Comments
JonLiu1993
added
the
category:community-triplet
JonLiu1993
added
the
category:vcpkg-bug
|
When I reproduce it on my machine I get the following error: This error also a bug in other issue: |
JonLiu1993
removed
the
category:community-triplet
I had to do this as a workaround for that particular error: brew install emscripten
eval "$(brew shellenv)"
export EMSCRIPTEN_ROOT="$HOMEBREW_PREFIX/opt/emscripten/libexec" |
|
You need to source one of the |
|
@asapha Did you find the solution for the "corrupted tree" problem? |
|
@JonLiu1993 @dg0yt The problem is that vcpkg tries to export vcpkg-cmake as a prefab, which of course cannot work. The following packages are already built and will be exported:
|
|
I only answered on an emscripten comment, but emscripten seem entirely unrelated. I don't know anything about the prefab export. It is easy to see that the export has assumptions which don't fit for vcpkg-cmake. There might be other reasons for port to have no |
vcpkg depend-info zlib --format=mermaidproduces the following diagram flowchart TD; zlib --> vcpkg-cmake;
Who knows what that means. Probably that the zlib PORT depends on vcpkg-cmake. After vcpkg install --triplet arm-neon-androidwe have 
There is no information that vcpkg-cmake:arm64-osx should be a host-only port. |
|
This installation is absolute correct and makes sense. |
|
The answer to your question is no. Android cannot run any host tools and the integration to the build system is done via gradle plug-in, based on meta data generated by vcpkg export --prefab. https://google.github.io/prefab/
|
|
I have managed to export the zlib vcpkg install zlib:arm-neon-android zlib:arm64-android zlib:x64-android zlib:x86-androidImportant It is mandatory to install all 4 of them! Delete the line
in the file .../vcpkg/installed/vcpkg/status vcpkg export zlib --triplet arm-neon-android --prefab --output-dir ./prefab --debug
|
No, but it was more appropriate to use manifest mode in my case. |
|
Thx for your suggestion. Unfortunately, the last installed triplet will be overwritten when using the manifest mode. #32631 I think I'll try conan + artifactory again. |
Describe the bug
Calling
vcpkg export --triplet arm64-android jsoncpp --prefab --prefab-maven --debug:fails on my machine. It leads to:Doing
rm -rf ~/dev/tools/vcpkg/ && rm -rf ~/.cache/vcpkgdoesn't helpEnvironment
13.5.2 (22G91)and13.6.2 (22G320)To Reproduce
vcpkg install jsoncpp --triplet arm64-android vcpkg export --triplet arm64-android jsoncpp --prefab --prefab-maven --debugTo Reproduce on a fresh Apple VM using Parallels
~/.zprofile:
Expected behavior
The export call should succeed or tell us what we can do to fix the issue.
Additional context
opusandantlr4vcpkg-cmake:XXX-androidpackages changes the export error tocopy_regular_recursive("/Users/azef/dev/tools/vcpkg/packages/vcpkg-cmake_x64-android/include", "/Users/azef/dev/tools/vcpkg/prefab/vcpkg-cmake/aar/prefab/modules/vcpkg-cmake/include"): No such file or directoryFailure logs
vcpkg export --triplet arm64-android jsoncpp --prefab --prefab-maven --debug:
The text was updated successfully, but these errors were encountered: