That was actually very useful. The main reason why I was trying to find some other ways to include third party libs (by now I've just either downloaded source files and compiled them, or used precomopiled binaries) is that I wanted to share my project across different platforms, and now I find it very convenient to have users download dependencies themselves and simply include the paths in DCMAKE_PREFIX_PATH, or if they're on linux it's handled even more.. "practically". So yea, thanks for the video!
Thank you. Nice to know how to do this with Visual Studio. I'm just wondering if you will come out with a static linked tutorial in the future? This way we don't have to worry about including DLL's with the exe.
Thanks for explanation. Can you just explain what would be the difference if I use: 1. package installed with apt-get (and where it is stored) 2. package installed in conda-env (and where it is stored)
Amazing video, but how to actually build such cmake libraries that actually produces this kind of install & cmake also produce the config.cmake automaticly
You actually can, I tend to just put all of my debug built packages in something like S:\sdks\debug-msvc. This way you can always just specify that path once and you're done. It ends up looking a lot like how packages are installed on Linux/macos. You'll see include, lib, etc. and a number of different lib and headers in there. Try it out! I should do a video pointing that out.
I was just curious where you were able to find all the information for this, CMake has some rather verbose documentation which seems to be a trend for C++ and so I wanted to know what resources you used or if you're just a CMake Wizard
really helped a lot. i was being stupid with 3rd party libs before
That was actually very useful. The main reason why I was trying to find some other ways to include third party libs (by now I've just either downloaded source files and compiled them, or used precomopiled binaries) is that I wanted to share my project across different platforms, and now I find it very convenient to have users download dependencies themselves and simply include the paths in DCMAKE_PREFIX_PATH, or if they're on linux it's handled even more.. "practically". So yea, thanks for the video!
Thank you for your guidance
You're welcome!
Thank you. Nice to know how to do this with Visual Studio. I'm just wondering if you will come out with a static linked tutorial in the future? This way we don't have to worry about including DLL's with the exe.
That's a good idea.
Thanks for explanation. Can you just explain what would be the difference if I use:
1. package installed with apt-get (and where it is stored)
2. package installed in conda-env (and where it is stored)
Thank you. But I cannot figure out why I don't see the "Cmake settings" button after right-clicking to the CMakeLists.txt
Amazing video, but how to actually build such cmake libraries that actually produces this kind of install & cmake also produce the config.cmake automaticly
ruclips.net/video/08f5Dav72aE/видео.html
I hope you find this one useful.
Thanks this was really good and to the point. btw it's a shame you can't just point to e.g. c:/packages but you have to specify every lib separately
You actually can, I tend to just put all of my debug built packages in something like S:\sdks\debug-msvc. This way you can always just specify that path once and you're done. It ends up looking a lot like how packages are installed on Linux/macos. You'll see include, lib, etc. and a number of different lib and headers in there. Try it out! I should do a video pointing that out.
I was just curious where you were able to find all the information for this, CMake has some rather verbose documentation which seems to be a trend for C++ and so I wanted to know what resources you used or if you're just a CMake Wizard
Sadly visual studio only opens the cmake settings as a json file for me :-(
Are you seeing a cmake presets JSON file or cmake settings?