Date: Fri, 15 Jun 2018 12:18:36 +0000
+1.
| -----Original Message-----
| From: tooling-bounces_at_[hidden] <tooling-bounces_at_[hidden]> On
| Behalf Of Boris Kolpackov
| Sent: Thursday, June 14, 2018 10:36 PM
| To: WG21 Tooling Study Group SG15 <tooling_at_[hidden]>
| Subject: Re: [Tooling] C++ project layout pool
|
| Rene Rivera <grafikrobot_at_[hidden]> writes:
|
| > You say in that post "There is talk at SG15 of coming up with a common
| > build description which I think will also require a common header/source
| > layout." Why do you think it requires a common directory layout?
|
| A common layout will make C++ packages easier to understand both to users
| and tools. So I think we should at least try to come up with one, and if
| not "required", then at least "recommended".
| _______________________________________________
| Tooling mailing list
| Tooling_at_[hidden]
| http://www.open-std.org/mailman/listinfo/tooling
| -----Original Message-----
| From: tooling-bounces_at_[hidden] <tooling-bounces_at_[hidden]> On
| Behalf Of Boris Kolpackov
| Sent: Thursday, June 14, 2018 10:36 PM
| To: WG21 Tooling Study Group SG15 <tooling_at_[hidden]>
| Subject: Re: [Tooling] C++ project layout pool
|
| Rene Rivera <grafikrobot_at_[hidden]> writes:
|
| > You say in that post "There is talk at SG15 of coming up with a common
| > build description which I think will also require a common header/source
| > layout." Why do you think it requires a common directory layout?
|
| A common layout will make C++ packages easier to understand both to users
| and tools. So I think we should at least try to come up with one, and if
| not "required", then at least "recommended".
| _______________________________________________
| Tooling mailing list
| Tooling_at_[hidden]
| http://www.open-std.org/mailman/listinfo/tooling
Received on 2018-06-15 14:29:09