rain cedar
Hi, so Im trying to plan and structure a project and Im thinking about how to handle dependencies in combination with repository.
So the questions is, how are you doing this?
1: Include prebuilt libraries in the repo for each platform?
2: Include the library source in the repo so each dev can built it for himself?
3: Git submodules?
4: Just list dependencies and version in the readme.
5: Vcpkg or Conan (What to do if I want lib to use higher or snapshot version than its in the catalogue?)
dapper driftBOT
wide stag
I use first three depending on what kind of library the library author provides, 4 sounds annoying.
no experience with 5
rain cedar
and would you say if it can be submoduled you would prefer it to be a submodule?
wide stag
nah, I don't like it since the code is "somewhere else", I usually prefer :header only libs>source code libs>static libs>dlls>install separate and add to PATH>submodules>readme/make other devs figure it out and suffer what you had to suffer
but that's just me, curious for second opinions
rain cedar
nice breakdown, thank you
Will wait for other opinions too
also to add
If you have built static or dlls
Do you have them for different platforms in the repo too?
so libs/coolLib/win/lib.dll
libs/coolLib/macx64/lib.dylib
libs/coolLib/macArm64/lib.dylib
wide stag
Yes, I have lib/linux/xyz.a lib/win/xyz.lib runtime/win/abc.dll etc
rain cedar
cool, thanks 🙂
unique tusk
Hi, so Im trying to plan and structure a project and Im thinking about how to ha...
1 or 2 depending upon whether the pre-built libraries aren't dependent on a specific version of complier. Which is what I prefer.
3rd option sounds good but when cloning it locally... the modules don't get cloned by default so you have to manually run clone to get the required modules which is annoying.
4th is more annoying than 3rd one.
5th I've never considered to try it.
azure barn
also submodules become very annoying if you change something, pushing submodule and then updating the parent and other stuff that comes along with it
sharp spear
use Conan, this is what it's for
5 is a bad category, vcpkg is terrible, Conan is fine
you can write your own Conan packages. if a Conan package is out of date, you can update it yourself
the same is true of vcpkg, but the main problem is that basically literally every vcpkg package is 8 years out of date, Conan is much better in this regard
rain cedar
Thanks for the input guys
Looks like the best way is to have source of the lib and/or prebuilt one directily in the repo
Will close this thread as solved tomorrow
rain cedar
!solved
dapper driftBOT
@rain cedar