[libgourou] Add new port and its dep
Describe the pull request
New port
-
What does your PR fix?
N/A
-
Which triplets are supported/not supported? Have you updated the CI baseline?
Linux, macOS
-
Does your PR follow the maintainer guide?
Yes
-
If you have added/updated a port: Have you run
./vcpkg x-add-version --alland committed the result?
Yes
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/
Please use vcpkg_install_copyright instead of file(INSTALL ...) for copyright file.
Other cl failures can be found in the log here: https://dev.azure.com/vcpkg/public/_build/results?buildId=81584&view=artifacts&pathAsName=false&type=publishedArtifacts
@Cheney-W That should do the trick.
I tried to test the usage on Linux machine with following CMakelist.txt:
cmake_minimum_required(VERSION 3.10)
project(test-project)
add_executable(main main.cpp)
find_package(libgourou CONFIG REQUIRED)
target_link_libraries(main PRIVATE gourou gourou_utils gourou_include gourou_compiler_flags)
and I got below errors:
CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
Target "main" links to target "pugixml::static" but the target was not
found. Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
Call Stack (most recent call first):
CMakeLists.txt:3 (add_executable)
CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
Target "main" links to target "pugixml::pugixml" but the target was not
found. Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
Call Stack (most recent call first):
CMakeLists.txt:3 (add_executable)
CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
Target "main" links to target "libzip::zip" but the target was not found.
Perhaps a find_package() call is missing for an IMPORTED target, or an
ALIAS target is missing?
Call Stack (most recent call first):
CMakeLists.txt:3 (add_executable)
CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
Target "main" links to target "OpenSSL::SSL" but the target was not found.
Perhaps a find_package() call is missing for an IMPORTED target, or an
ALIAS target is missing?
Call Stack (most recent call first):
CMakeLists.txt:3 (add_executable)
CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
Target "main" links to target "CURL::libcurl" but the target was not found.
Perhaps a find_package() call is missing for an IMPORTED target, or an
ALIAS target is missing?
Call Stack (most recent call first):
CMakeLists.txt:3 (add_executable)
For fixing above errors, I think you should add below contents into the https://github.com/SamuelMarks/libgourou/blob/cmake/cmake/Config.cmake.in file:
include(CMakeFindDependencyMacro)
find_dependency(CURL)
find_dependency(libzip)
find_dependency(OpenSSL)
find_dependency(pugixml)
@Cheney-W Darn, it's been open for 2 years and no activity for 3 months (whence someone had built solution on their fork): https://gitlab.kitware.com/cmake/cmake/-/issues/20511
I'll make the changes you suggested & thanks
@SamuelMarks Could you please apply my suggestions?
@Cheney-W I thought I did a week ago? - Or did I miss something?
I added some comments in vcpkg.json file before, about the "version" and "supports", could you please take a look?
@SamuelMarks Are you still working on this PR?
https://github.com/microsoft/vcpkg/pull/28037/files#r1034336129 https://github.com/microsoft/vcpkg/pull/28037/files#r1034336172 https://github.com/microsoft/vcpkg/pull/28037/files#r1034349135 https://github.com/microsoft/vcpkg/pull/28037/files#r1034336205 https://github.com/microsoft/vcpkg/pull/28037/files#r1034336223 https://github.com/microsoft/vcpkg/pull/28037/files#r1034349662
Could you please apply above suggestions? Thank you!
@SamuelMarks Are you still working on this PR?
Yes, I thought maybe I'd add Windows support first then send it through
Otherwise it's basically ready at is
OK, please apply my suggestions by the way when you add new changes.
Otherwise it's basically ready at is
Oops, sorry this slipped through review cracks for so long; I'm guessing because it is still marked as 'draft'. Can you confirm that you still want this change as is by marking 'ready for review'?
Thanks!