3 ms·

> You can speak for everyone. Not really. I only use header-only libraries and dependency management is a breeze for me. I check each library out as a git subm

> You can speak for everyone. Not really. I only use header-only libraries and dependency management is a breeze for me. I check each library out as a git submodule into a third-party subdirectory in my project directory, point the includes path at it and off I go. When I want to upgrade, I pull the git tag/branch/commit I want and recompile. Its pretty simple.

adamnemecek 5y ago
I mean that's cool but you are definitely working against the language as opposed to having the language support you. Also this works nicely for self contained dependencies, and much less nicely for not self contained dependencies.
- dkersten 5y ago
  > you are definitely working against the language How so? > Also this works nicely for self contained dependencies, and much less nicely for not self contained dependencies. Doesn't matter. You said: "You can speak for everyone." which is simply not true, as I have outlined. You didn't say anything about not self contained dependencies or whatnot. The person you replied to said "I spent an unconscionable amount of time managing dependencies and libraries in C++" and I... well, don't. So clearly not everybody does.
  - adamnemecek 5y ago
    Right, but not all problems can solved with header only frameworks.
    - dkersten 5y ago
      I did use Bullet physics not too long ago, which most definitely isn't header-only, but the exact same approach worked there too. Git submodule, set include path. The only difference is that I also told my build tool to build its sources and package them into an .a archive, which I linked against. It was no trouble at all.
      - dkersten 5y ago
        Too late to edit: yes, I know this doesn't work for everything and won't work for everyone, but its worked great for me, so my point is simply that your assertion that everyone has difficulties dealing with dependencies is false. Some people for sure do, but there are people, like me, who don't.

adamnemecek 5y ago

I mean that's cool but you are definitely working against the language as opposed to having the language support you. Also this works nicely for self contained dependencies, and much less nicely for not self contained dependencies.

dkersten 5y ago
> you are definitely working against the language How so? > Also this works nicely for self contained dependencies, and much less nicely for not self contained dependencies. Doesn't matter. You said: "You can speak for everyone." which is simply not true, as I have outlined. You didn't say anything about not self contained dependencies or whatnot. The person you replied to said "I spent an unconscionable amount of time managing dependencies and libraries in C++" and I... well, don't. So clearly not everybody does.
- adamnemecek 5y ago
  Right, but not all problems can solved with header only frameworks.
  - dkersten 5y ago
    I did use Bullet physics not too long ago, which most definitely isn't header-only, but the exact same approach worked there too. Git submodule, set include path. The only difference is that I also told my build tool to build its sources and package them into an .a archive, which I linked against. It was no trouble at all.
    - dkersten 5y ago
      Too late to edit: yes, I know this doesn't work for everything and won't work for everyone, but its worked great for me, so my point is simply that your assertion that everyone has difficulties dealing with dependencies is false. Some people for sure do, but there are people, like me, who don't.