Describe the bug
With the current master branch (commit 1be75a2) the use of custom ports at some point prevents to install any further non-custom port from vcpkg.
Environment
- OS: Windows
- Compiler: VS2019
To Reproduce
git clone https://github.com/microsoft/vcpkg C:/vcpkg
git clone https://github.com/robotology/robotology-vcpkg-binary-ports C:/robotology-vcpkg-binary-ports
C:/vcpkg/bootstrap-vcpkg.sh
C:/vcpkg/vcpkg.exe --overlay-ports=C:/robotology-vcpkg-binary-ports install --triplet x64-windows ipopt-binary
C:/vcpkg/vcpkg.exe install --triplet x64-windows asio
The last command will fail with the following error:
Computing installation plan...
Error: while loading ipopt-binary:x64-windows: Port definition not found.
Please run "vcpkg remove ipopt-binary:x64-windows" and re-attempt.
Expected behavior
The asio port should be installed correctly, even if the custom port ipopt-binary had been installed before.
Failure logs
See robotology/robotology-vcpkg-ports#5 for a CI script that is working fine in 2020.01 and 2019.12, and failing in master due to this bug.
Describe the bug
With the current
masterbranch (commit 1be75a2) the use of custom ports at some point prevents to install any further non-custom port from vcpkg.Environment
To Reproduce
The last command will fail with the following error:
Expected behavior
The
asioport should be installed correctly, even if the custom portipopt-binaryhad been installed before.Failure logs
See robotology/robotology-vcpkg-ports#5 for a CI script that is working fine in 2020.01 and 2019.12, and failing in master due to this bug.