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

[openmvg] Build error on x64-linux #43106

Open
poulpoulsen opened this issue Jan 5, 2025 · 7 comments · May be fixed by #43117
Open

[openmvg] Build error on x64-linux #43106

poulpoulsen opened this issue Jan 5, 2025 · 7 comments · May be fixed by #43117
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@poulpoulsen
Copy link

Package: openmvg[core,openmp]:[email protected]#1
Host Environment
Host: x64-linux
Compiler: GNU 13.3.0
vcpkg-tool version: 2024-12-09-1005b78fa1bf1dde1a20c2734cba4ea61ca94d9a vcpkg-scripts version: 65be701 2025-01-03 (2 days ago)
To Reproduce
vcpkg install openmvg[core,openmp]
Failure logs
Downloading openMVG-openMVG-01193a245ee3c36458e650b1cf4402caad8983ef.tar.gz
Successfully downloaded openMVG-openMVG-01193a245ee3c36458e650b1cf4402caad8983ef.tar.gz.
-- Extracting source /home/held/src/vcpkg/downloads/openMVG-openMVG-01193a245ee3c36458e650b1cf4402caad8983ef.tar.gz
-- Applying patch build_fixes.patch
-- Applying patch 0001-eigen_3.4.0.patch
-- Applying patch no-absolute-paths.patch
-- Using source at /home/held/src/vcpkg/buildtrees/openmvg/src/caad8983ef-b9f8fe8a38.clean
-- Found external ninja('1.11.1').
-- Configuring x64-linux
-- Building x64-linux-dbg
-- Building x64-linux-rel
CMake Error at installed/x64-linux/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake:81 (message):
'/home/held/src/vcpkg/packages/openmvg_x64-linux/debug/share/openmvg' does
not exist.
Call Stack (most recent call first):
ports/openmvg/portfile.cmake:86 (vcpkg_cmake_config_fixup)
scripts/ports.cmake:196 (include)

@jimwang118 jimwang118 self-assigned this Jan 6, 2025
@JackBoosY
Copy link
Contributor

JackBoosY commented Jan 6, 2025

install(FILES "${CMAKE_CURRENT_BINARY_DIR}/OpenMVGConfig.cmake"
        DESTINATION ${CMAKE_INSTALL_LIBDIR}/openMVG/cmake)

Caused by case sensitive

@JackBoosY JackBoosY linked a pull request Jan 6, 2025 that will close this issue
7 tasks
@JackBoosY
Copy link
Contributor

JackBoosY commented Jan 6, 2025

After double check the code, this may because VCPKG_BUILD_TYPE is set to some value, which caused path ${CURRENT_PACKAGES_DIR}/debug/share/openMVG/ is not created.

@jimwang118 jimwang118 added the category:port-bug The issue is with a library, which is something the port should already support label Jan 6, 2025
@dg0yt
Copy link
Contributor

dg0yt commented Jan 6, 2025

After double check the code, this may because VCPKG_BUILD_TYPE is set to some value, which caused path ${CURRENT_PACKAGES_DIR}/debug/share/openMVG/ is not created.

This build is not having VCPKG_BUILD_TYPE defined:

-- Building x64-linux-dbg
-- Building x64-linux-rel

@JackBoosY
Copy link
Contributor

After double check the code, this may because VCPKG_BUILD_TYPE is set to some value, which caused path ${CURRENT_PACKAGES_DIR}/debug/share/openMVG/ is not created.

This build is not having VCPKG_BUILD_TYPE defined:

-- Building x64-linux-dbg
-- Building x64-linux-rel

Yeah you are correct, but why our CI doesn't have this error?

@dg0yt
Copy link
Contributor

dg0yt commented Jan 6, 2025

install(FILES "${CMAKE_CURRENT_BINARY_DIR}/OpenMVGConfig.cmake"
DESTINATION ${CMAKE_INSTALL_LIBDIR}/openMVG/cmake)

CMAKE_INSTALL_LIBDIR does not lead to missing destination:

'/home/held/src/vcpkg/packages/openmvg_x64-linux/debug/share/openmvg' does
not exist.

Probably just another package with different destination on Windows vs. non-Windows.

@dg0yt
Copy link
Contributor

dg0yt commented Jan 6, 2025

Yeah you are correct, but why our CI doesn't have this error?

$ grep openmvg scripts/ci.baseline.txt 
openmvg:x64-linux=fail

@JackBoosY
Copy link
Contributor

I tried to install this port on my MacBook and successfully without any changes.
Also I checked the record in ci.baseline but got nothing.

God knows what happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants