HN Theater @HNTheaterMonth

Is this like llbuild?

https://www.youtube.com/watch?v=b_T-eCToX1I

https://github.com/apple/swift-llbuild

I remember watching the talk awhile ago, but haven't kept up with its progress. It's about using LLVM as a library to eliminate duplicate work, as far as I remember.

I think it was for C++ as well as Swift.

https://github.com/apple/swift-llbuild may be too low-level for what you envision, but captures a lot of your ideas, I think.

https://llvm.org/devmtg/2016-11/#abstracts has a presentation. It focuses on compiling with clang, but the system is more flexible. Slides at https://llvm.org/devmtg/2016-11/Slides/Dunbar-NewArchitectur..., matching video is at https://youtu.be/b_T-eCToX1I.

If you are on Windows, VS 2015 and the upcoming VS 2016 have lots of improvements regarding compile times.

https://blogs.msdn.microsoft.com/vcblog/2016/10/05/faster-c-...

https://blogs.msdn.microsoft.com/vcblog/2016/10/26/recommend...

https://channel9.msdn.com/Events/Connect/2016?sort=status&di...

Apple is also doing a similar work regarding incremental C and C++ builds, based on the work they did for Swift

https://www.youtube.com/watch?v=b_T-eCToX1I

C++ builds can be made bearable if you don't go crazy with template meta-programming, do forward declarations, only expose actually public data on the headers, instantiate most use templates.

But specially do use binary libraries, even across application modules. Don't spend endless time recompiling code that doesn't change.

⬐ weavie

I suspect with 10+ year old hardware he will not be on Windows.

⬐ pjmlp

I do have 10+ year old hardware on Windows, namely 7 and 10 versions of it.

IT only changes workstations when they break down or they cannot fulfill project requirements.

⬐ i336_

You're right: Slackware :)

This ThinkPad T43 turned 10 this year :P

(In all fairness, my T60 is 9 years old now.)

⬐ Matthias247

> C++ builds can be made bearable if you don't go crazy with template meta-programming, do forward declarations, only expose actually public data on the headers, instantiate most use templates.

Exactly. E.g. QT based applications (which rely on object orientation, inheritance and virtual methods) compile reasonably fast. However the template oriented style (e.g. found in boost libraries) can increase compile times A LOT. I had more than factor 10 for one of my libraries that I ported from having boost as a dependency to QT. Although the template oriented style might really work faster at runtime, because there's less need for virtual function calls and other indirections.