3 ms·
I think (some of) the main reasons are: - there is no standard cross-platform build system and directory structure for C/C++ projects, a dependency manager eit
by flohofwoe 10y ago
I think (some of) the main reasons are:
- there is no standard cross-platform build system and directory structure for C/C++ projects, a dependency manager either needs to be super-flexible and enable to combine projects with completely different build systems (which is impossible I guess?), or come with its own build system and enforce a directory structure (like Rusts cargo)
- complex C++ projects are not very compatible with each other since they use different subsets of the C++ language and the standard library, this makes it often hard or impossible to integrate external C++ code
This is why header-only, or single header/source pair C or (simple) C++ projects make so much sense, they are often trivial to integrate with your own code.
However, there are some movements into the right direction, cmake seems to establish itself as the standard build system, and there's also https://www.conan.io/ https://www.conan.io/
It would be better though if the C++ Standard Committee would get their act together and instead of stuffing more and more useless crap into the C++ standard, use the time and resources to establish a dependency manager standard (along with a proper module system), and let the language users move all the 'useless crap' there.
- CyberDildonics 10y ago> complex C++ projects are not very compatible with each other since they use different subsets of the C++ language and the standard library, this makes it often hard or impossible to integrate external C++ code How does this make sense? If a project uses a certain style, that doesn't make it incompatible with another style by any measure.
- flohofwoe 10y agoIf a project disables exceptions and RTTI, other projects which uses those won't compile (at least on GCC and clang). Many low level C++ projects don't use std containers, std::string or iostreams, etc...
- wst_ 10y agoDependencies may be compiled and then downloaded as package. In Java dependencies, theoretically, could be compiled during the project building, but they are provided as compiled anyway. It is faster that way. Here you have different platforms, but I guess it could be done anyway.