3 ms·
You don't have to change #include paths in C++ (or Java imports) code when you move your project from github to bitbucket.
by zerr 10y ago
You don't have to change #include paths in C++ (or Java imports) code when you move your project from github to bitbucket.
- XorNot 10y agoHave you looked at the build system of a C++ project lately? Or a Java project? It's not like that's some super-elegant not-at-all-rolling-catastrophe of a system. Java and Node, for example, don't solve anything - to get something that builds sensibly they both entirely depend on "external service" being always available and enforcing naming (see the leftpad fiasco). C/C++ are the source of the term "dependency hell".
- deleted 10y ago[deleted]
- PopsiclePete 10y agoI've had to deal with CMake as well as automake/autoconf at work recently and I'll take Go's system of fetching/building any day over the Wild West that is the C/C++ eco-system.