CppCon 2018

Although we have a panel on packaging and modules, and have had plenty of presentations on build systems, we still haven't gotten a group of people into a room to discuss build systems and all the things we can do better to improve our build system story.

What can we do to move the entire community forward towards a federated build system environment? What obstacles do we have on improving the boilerplate that each project has to create? Is the concept of a zero config build system that difficult? Is C++ doomed to require separate macro languages to construct our build, while other languages (e.g., Haskell, C#, OCaml, Rust, Ruby, Python, Go, Typescript, etc.) can and do express their builds natively? Why can't we just let my build system glob these files for me? Why can't we tie modules to the filesystem? Is making the compiler a build system really such a bad idea?

Join our panelists, each of whom has given a talk on build systems at CppCon as they debate and try to compromise over C++'s future with building our projects. This panel will focus less on packaging and more on building our software.