Vcpkg: [drogon:x64-linux] build failure

Created on 19 Aug 2020  ยท  3Comments  ยท  Source: microsoft/vcpkg

Host Environment

  • OS: ArchLinux (kernel 5.8.1)
  • Compiler: GCC 10.1.0, Clang 10.0.1

To Reproduce
Steps to reproduce the behavior:
./vcpkg install drogon

โฏ ./vcpkg install drogon
Computing installation plan...
The following packages will be built and installed:
    drogon[core]:x64-linux
Detecting compiler hash for triplet x64-linux...
Starting package 1/1: drogon:x64-linux
Building package drogon[core]:x64-linux...
Could not locate cached archive: /home/valery/.cache/vcpkg/archives/40/4044b973b544d020a14eb361611f43c7de79d9e4.zip
-- Using cached /home/valery/Cache/vcpkg/downloads/an-tao-drogon-v1.0.0-beta20.tar.gz
-- Cleaning sources at /home/valery/Cache/vcpkg/buildtrees/drogon/src/0.0-beta20-4b821353ac.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/valery/Cache/vcpkg/downloads/an-tao-drogon-v1.0.0-beta20.tar.gz
-- Applying patch vcpkg.patch
-- Applying patch drogon_ctl_install.patch
-- Applying patch pg.patch
-- Using source at /home/valery/Cache/vcpkg/buildtrees/drogon/src/0.0-beta20-4b821353ac.clean
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel
CMake Error at scripts/cmake/vcpkg_fixup_cmake_targets.cmake:72 (message):

  '/home/valery/Cache/vcpkg/packages/drogon_x64-linux/debug/lib/cmake/drogon'
  does not exist.
Call Stack (most recent call first):
  ports/drogon/portfile.cmake:23 (vcpkg_fixup_cmake_targets)
  scripts/ports.cmake:79 (include)


Error: Building package drogon:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: drogon:x64-linux
  Vcpkg version: 2020.06.15-unknownhash
port-bug

All 3 comments

Hi @48d90782
Thanks for posting this issue.

There is a PR #13007 to fix this issue now. Let's wait for the PR merged.

@NancyLi1013 I can confirm that PR #13007 fixes the issue.

@48d90782
Thanks for your reply.

I'm closing this issue for now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

LilyWangL picture LilyWangL  ยท  3Comments

F0I0l0I0P picture F0I0l0I0P  ยท  3Comments

ThinkalVB picture ThinkalVB  ยท  3Comments

cskrisz picture cskrisz  ยท  3Comments

madkoala picture madkoala  ยท  3Comments