C++ Logo


Advanced search

Re: P2577R0 - C++ Modules Discovery in Prebuilt Library Releases

From: Daniel Ruoso <daniel_at_[hidden]>
Date: Sat, 30 Apr 2022 12:53:25 -0400
I just uploaded a revised version of this paper. It doesn't change the
proposal per se, but it just explains how this would also be usable
for the standard library.

● R1: Include the standard library in the example output of the
translation of linker arguments. This will allow the standard library
to advertise the modules it offers in the same way as any other
library. This is not a change in the proposal per-se, but just an
expansion of the usability to also include the standard libra


Em seg., 11 de abr. de 2022 às 18:02, Steve Downey <sdowney_at_[hidden]> escreveu:
> One thing I like about connecting to linker artifacts is that it restricts the problem from how to build some module interface to how to build an ABI equivalent interface for a particular binary in a particular ecosystem.
> It's still not a trivial problem, but it's one we have some experience in providing solutions for.
> On Mon, Apr 11, 2022, 17:40 Daniel Ruoso via SG15 <sg15_at_[hidden]> wrote:
>> Hello,
>> As discussed in previous meetings, we need to solve the problem on how
>> to solve the discovery of the metadata for modules. This paper uses
>> the "linker arguments" idea.
>> It makes the caveat about "interface-unit-only module libraries" as
>> well as to the fact that this will eventually be superseded by proper
>> package management (although I think it will remain useful as a
>> lowest-common-denominator option even then).
>> https://isocpp.org/files/papers/P2577R0.pdf please take a look and let
>> me know what you think.
>> daniel
>> _______________________________________________
>> SG15 mailing list
>> SG15_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg15

Received on 2022-04-30 16:53:37