alt Hacker News>There are of course good ways of building C++, but those are the exception rather than the standard.
What are the good ways?
Replies
lstodd • yesterday at 9:50 PM
"Do not do it" looks like the winning one nowadays.
>There are of course good ways of building C++, but those are the exception rather than the standard.
What are the good ways?
"Do not do it" looks like the winning one nowadays.
Build everything from source within a single unified workspace, cache whatever artifacts were already built with content-addressable storage so that you don't need to build them again.
You should also avoid libraries, as they reduce granularity and needlessly complexify the logic.
I'd also argue you shouldn't have any kind of declaration of dependencies and simply deduce them transparently based on what the code includes, with some logic to map header to implementation files.