How add this library to application with vcpkg in manifest mode? #2689
Labels
building-system
Related to building sytem
question
Questions about usage, configurations, or issues that don’t clearly classify as bugs
I'm almost newbie in using vcpkg in manifest mode.
What I want is to compile Mega SDK as static library which I can use in CMake application
It would be good to receive instructions to compile it in isolated way (in devcontainer)
Previously I've compiled SDK using now obsolete Autotools way. As result artefact I received library and PkgConfig's
libmega.pc
file. Then I using library in CMake project using following commands:Now with new vcpkg.json manifest I can compile it in devcontainer using instructions from README.md file.
Then if I execute
make install
command with customCMAKE_INSTALL_PREFIX
path I've received only partial result. Resulting folder contains:megaapi.h
.sdklib.pc
file*Config.cmake
and*Targets.cmake
files where problems locatedThose CMake points
MEGA::SDKlib
target to include folders and libs using absolute paths of it dependencies likeunofficial-sodium::sodium_config_public
,libswresample.so
and so on. In my example it looks like/workspaces/sdk-7.10.1/build/vcpkg_installed/x64-linux-mega/debug/lib/libavcodec.so
My guess is to create my application using vcpkg/CMake with somehow pointing to this library.
Maybe I need to include it as git submodule but in that case I need to tell vcpkg to include it as library and dependency of my application.
In some other libraries I saw usage instructions to add them as vcpkg git repository in
vcpkg-configuration.json
and then add port independencies
section invcpkg.json
.But in that cases libraries it self was standard CMake projects. And custom vcpkg was in separate git repository with compile instructions in
portfile.cmake
script.Do anyone uses Mega SDK as library in own project using vcpkg?
Can you provide complete instructions to include it as dependency with passing features options like
use-freeimage
,use-ffmpeg
or disabling some of them?The text was updated successfully, but these errors were encountered: