Hi Jon,

I've given talks on how it works at MeetingC++ 2016 and 2017, and CppCon
2018. We're using one of those tools at work too to autogenerate 70% of our
build scripts (CMake) for a very large project (1000+ components). You can
find the tool repositories on
https://github.com/tomtom-international/cpp-dependencies and
https://github.com/dascandy/evoke.

I'm mostly advocating the approach as a valid one though, rather than the
specific tools. I believe John Lakos' Large Scale C++ Software Design also
allures to it as a valid approach.

Regards,
Peter Bindels

On Wed, 19 Dec 2018 at 13:11, Jon Chesterfield <
jonathanchesterfield_at_[hidden]> wrote:

> Hi Peter,
>
> Date: Wed, 19 Dec 2018 08:48:54 +0100
>> From: Peter Bindels <dascandy_at_[hidden]>
>
>
>> I, for one, have stopped writing build files about 4 years ago and I
>> haven't missed them one bit.
>>
>
> How have you achieved this excellent result?
>
> I spent a long time trying to write a single build script that would infer
> dependencies from the filesystem layout and then just works as more files
> are added / moved. That's sort of functional, but it struggles with code
> generators and still contains a list of what libraries various executables
> should be linked against.
>
> I'd very much like a good solution to this.
>
> Cheers
>
> Jon
>
> _______________________________________________
> Tooling mailing list
> Tooling_at_[hidden]
> http://www.open-std.org/mailman/listinfo/tooling
>