Re:All C++20 core language features with examples
by humanrebar on Wednesday April 07, 2021 @03:30PM
(#26729874)
Do the Go sources on GitHub use waf, make, CMake, bazel, or something entirely bespoke? Or is a common build system assumed?
[ Parent
| on HN ]
Re:All C++20 core language features with examples
by coder543 on Wednesday April 07, 2021 @03:40PM
(#26730021)
Go just uses the Go build system, which is common to all Go projects, so... it assumes a common build system.
Some people do occasionally use Bazel or other build systems on top of the Go build system for complicated monorepos.
Re:All C++20 core language features with examples
by humanrebar on Wednesday April 07, 2021 @03:51PM
(#26730196)
Right. C++ has a chicken-and-the-egg problem in that neither its build not packaging ecosystem have even de facto standards. GitHub URLs don't solve either problem.
Re:All C++20 core language features with examples
by coder543 on Wednesday April 07, 2021 @04:01PM
(#26730368)
I think everyone agrees that a common build system is a necessary step if any of this is going to work.
Thinking about how much or how little would be required beyond a common build system in order to get a working package management system is still a valid thing to do.
Re:All C++20 core language features with examples
by humanrebar on Wednesday April 07, 2021 @06:50PM
(#26732557)
I expect it is necessary to keep build configuration portable with respect to packaging and environment configuration. In other words, I expect downloading from URLs in Makefiles and CMakeLists to be a local maximum.
Keeping a parallel set of instructions or metadata that includes specific URLs and such might work, though. As long as you can skip all that when a system package, filesystem path, or git submodule is more appropriate.