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

file COPY cannot read symlink #84

Closed
alex-taffe opened this issue May 28, 2021 · 1 comment
Closed

file COPY cannot read symlink #84

alex-taffe opened this issue May 28, 2021 · 1 comment

Comments

@alex-taffe
Copy link

I’m not really sure if this is an issue with CMake, vcpkg, or run-vcpkg but it isn’t happening locally, so I’m guessing the latter. When trying to install libusb, I get the error:

CMake Error at scripts/cmake/vcpkg_install_msbuild.cmake:160 (file):
    file COPY cannot read symlink
    "D:/a/AutoML/AutoML/vcpkg/buildtrees/libusb/src/3ae1ed06fa-f8218372d8.clean/README"
    to duplicate at
    "D:/a/AutoML/AutoML/vcpkg/buildtrees/libusb/x64-windows-rel/3ae1ed06fa-f8218372d8.clean/README":
    No such file or directory.
  Call Stack (most recent call first):
    ports/libusb/portfile.cmake:42 (vcpkg_install_msbuild)
    scripts/ports.cmake:79 (include)

  Error: Building package libusb:x64-windows failed with: BUILD_FAILED

My vcpkg.txt is:

--triplet
x64-windows
libwebsockets
libusb

My GitHub action is using windows-latest and the step for vcpkg is:

    - name: Install vcpkg
      uses: lukka/run-vcpkg@v7
      env:
        ACTIONS_ALLOW_UNSECURE_COMMANDS: true
      with:
        vcpkgDirectory: '${{ github.workspace }}/vcpkg'
        vcpkgArguments: '@${{ github.workspace }}/vcpkg.txt'
        appendedCacheKey: ${{ hashFiles(env.vcpkgResponseFile) }}

The vcpkg submodule is on 2020.07. Some people were saying they were having this issue with OneDrive (microsoft/vcpkg#2488) but seeing as this library is doubtful to use OneDrive, I’m not sure. I can’t reproduce locally so I’m not sure what’s going on

@alex-taffe
Copy link
Author

Actually, updating vcpkg to 2021.05.12 solved the issue, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant