Yes it's been discussed, notably with a focus on modules, which need more information that is typically required currently. We felt it was too far outside what the standard currently talks about (for instance it goes out of its way to not rely on concepts like "files". See https://eel.is/c++draft/cpp.include#2 for an example) to be part of the C++ standard itself, but could be part of some other standard document. Minutes of a discussion about this: https://wiki.edg.com/bin/view/Wg21kona2022/P2656-20221109-SG15


________________________________
From: SG15 <sg15-bounces_at_[hidden]> on behalf of James via SG15 <sg15_at_[hidden]>
Sent: Tuesday, November 19, 2024 3:51 AM
To: sg15_at_[hidden] <sg15_at_[hidden]g>
Cc: James <james.business.84_at_[hidden]>
Subject: Re: [isocpp-sg15] std::build (Standardized Project Description Format) (Harald Achitz)

What I meant is a format that is officially part of the C++ standard. The standard would define how it works, and build systems would implement support for it.

On Sat, Nov 16, 2024 at 3:00 PM <sg15-request_at_[hidden]<mailto:sg15-request_at_[hidden]>> wrote:
Send SG15 mailing list submissions to
        sg15_at_[hidden]<mailto:sg15_at_lists.isocpp.org>

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isocpp.org/mailman/listinfo.cgi/sg15
or, via email, send a message with subject or body 'help' to
        sg15-request_at_[hidden]<mailto:sg15-request_at_[hidden]>

You can reach the person managing the list at
        sg15-owner_at_[hidden]ocpp.org<mailto:sg15-owner_at_[hidden]>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of SG15 digest..."


Today's Topics:

   1. Re: std::build (Standardized Project Description Format)
      (Harald Achitz)


----------------------------------------------------------------------

Message: 1
Date: Sat, 16 Nov 2024 09:18:50 +0100
From: Harald Achitz <harald_at_[hidden]<mailto:harald_at_[hidden]>>
To: sg15_at_[hidden]<mailto:sg15_at_[hidden]cpp.org>
Subject: Re: [isocpp-sg15] std::build (Standardized Project
        Description Format)
Message-ID: <b168c496-a559-44e0-a218-ae824d3cd22f_at_[hidden]<mailto:b168c496-a559-44e0-a218-ae824d3cd22f_at_[hidden]>>
Content-Type: text/plain; charset=UTF-8; format=flowed

Probably this: https://cps-org.github.io/cps/


On 2024-11-14 23:53, James via SG15 wrote:
>
> Has there been any consideration for establishing a standardized
> format to describe C++ projects that could be universally recognized
> by different build systems? This wouldn?t involve creating a new build
> system, but rather defining a common file format that accurately
> describes project structure, dependencies, and build requirements in a
> standardized way.
>
> The goal would be to improve interoperability and developer experience
> across different build systems and generators, also allowing projects
> to seamlessly transition between them without modifications to the
> project file itself.
>
> Additionally such a change could improve tooling and IDEs, enhancing
> the developer experience even more!
>
>
> _______________________________________________
> SG15 mailing list
> SG15_at_[hidden]<mailto:SG15_at_[hidden]>
> https://lists.isocpp.org/mailman/listinfo.cgi/sg15


------------------------------

Subject: Digest Footer

_______________________________________________
SG15 mailing list
SG15_at_[hidden]<mailto:SG15_at_[hidden]g>
https://lists.isocpp.org/mailman/listinfo.cgi/sg15


------------------------------

End of SG15 Digest, Vol 55, Issue 4
***********************************