C++ Logo

sg15

Advanced search

Re: [Tooling] Evening Session

From: Gabriel Dos Reis <gdr_at_[hidden]>
Date: Mon, 12 Mar 2018 13:20:45 +0000
I will copy-n-paste my earlier suggestions here:

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


From: tooling-bounces_at_[hidden] <tooling-bounces_at_[hidden]> On Behalf Of Rene Rivera
Sent: Sunday, March 11, 2018 10:06 AM
To: WG21 Tooling Study Group SG15 <tooling_at_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<http://aka.ms/LearnAboutSpoofing>

Feedback<http://aka.ms/SafetyTipsFeedback>

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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frobot-dreams.net%2F&data=04%7C01%7Cgdr%40microsoft.com%7C29e096f0e7ae46fa0a1208d5877270f3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636563847976503964%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C100&sdata=1m2J%2Bo50SND6TfM3%2BVujubQ4D2Kqv0br1sD3EKG1eeg%3D&reserved=0>

Received on 2018-03-12 14:20:50