I will copy-n-paste my earlier suggestions here:

Commonly agreed up way to describe C++ components for build systems – no, I am not aiming for a “universal” build system (not a goal)
Packing for C++ components – this ties into (1) I suspect.
Tools for migration, especially as we consider modules.

From: tooling-bounces@open-std.org <tooling-bounces@open-std.org> On Behalf Of Rene Rivera
Sent: Sunday, March 11, 2018 10:06 AM
To: WG21 Tooling Study Group SG15 <tooling@open-std.org>
Subject: Re: [Tooling] Evening Session

This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing

Feedback

I'm not going to be there.. But here's my list of todo items in tooling:

* Compile invocation standard (I'm preparing a paper and proof of concept library for this).

* Standard package format.

* Standard interoperation between build system and package managers.

* General evaluation of ecosystem with regards to making it easy for everyone to develop with C++.

For SG15 I would really like it to follow the SG14 model of being as open as possible to discussions and contributions from the industry.

-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net