Date: Thu, 29 Jan 2026 17:36:11 +0000
Hi, look here
https://github.com/ecostd/standard
this is not iso
also, subscribe to this group, then you get invitation to the monthly
meeting (not iso)
https://groups.google.com/g/cxx-ecosystem-evolution
and there is a ecosystem_evolution slack channel on the cpplang.slack.com
here, on iso, there is still the WG15 mailinglist, not very active but from
time to time there are topics
hope that helps
/Harald
On Friday, 23 January 2026 14:17:25 (+01:00), geguji60--- via Std-Proposals
wrote:
> Subject: Follow-up: Presenting Initial Design Concepts for Standardizing
Build Configuration
>
> Dear C++ Standards Committee,
>
> Continuing from my previous communication, I wish to present some
preliminary design concepts concerning build configuration. Initially, I
propose adopting TOML as the configuration file format, owing to its
superior intuitiveness and readability when compared to alternatives like
XML, JSON, or others.
>
> I have also thoroughly evaluated existing C++ build tools. For instance,
while CMake boasts robust functionality, its syntax can be somewhat
non-standard, which I believe detracts from its suitability for a
contemporary build system. Similarly, tools like Make, though historically
significant, now appear somewhat antiquated in light of current development
demands.
>
> For the advancement of C++, I am convinced that projects would greatly
benefit from a build configuration file that is both straightforward and
intuitive. This conviction has led me to select TOML as the basis for my
design. Moreover, I am actively engaged in developing a tool that embodies
this concept.
>
> Below is a sample of the syntax I am advocating:
>
> Target Definition:
> [target.main]
> flags = ["-O2"]
> src = ["src/main.cpp"]
> buildtype = "Release"
> A Basic Project Example:
> [project]
> name = "Hello C++"
> version = "0.1"
> license = "MIT"
> standard = "c++20"
> toolchain = "Clang"
>
> [target.main]
> # Refer to the target definition above
> # ...
>
> I am eager to receive any initial insights or feedback regarding this
proposed direction.
>
> [Your Name]
https://github.com/ecostd/standard
this is not iso
also, subscribe to this group, then you get invitation to the monthly
meeting (not iso)
https://groups.google.com/g/cxx-ecosystem-evolution
and there is a ecosystem_evolution slack channel on the cpplang.slack.com
here, on iso, there is still the WG15 mailinglist, not very active but from
time to time there are topics
hope that helps
/Harald
On Friday, 23 January 2026 14:17:25 (+01:00), geguji60--- via Std-Proposals
wrote:
> Subject: Follow-up: Presenting Initial Design Concepts for Standardizing
Build Configuration
>
> Dear C++ Standards Committee,
>
> Continuing from my previous communication, I wish to present some
preliminary design concepts concerning build configuration. Initially, I
propose adopting TOML as the configuration file format, owing to its
superior intuitiveness and readability when compared to alternatives like
XML, JSON, or others.
>
> I have also thoroughly evaluated existing C++ build tools. For instance,
while CMake boasts robust functionality, its syntax can be somewhat
non-standard, which I believe detracts from its suitability for a
contemporary build system. Similarly, tools like Make, though historically
significant, now appear somewhat antiquated in light of current development
demands.
>
> For the advancement of C++, I am convinced that projects would greatly
benefit from a build configuration file that is both straightforward and
intuitive. This conviction has led me to select TOML as the basis for my
design. Moreover, I am actively engaged in developing a tool that embodies
this concept.
>
> Below is a sample of the syntax I am advocating:
>
> Target Definition:
> [target.main]
> flags = ["-O2"]
> src = ["src/main.cpp"]
> buildtype = "Release"
> A Basic Project Example:
> [project]
> name = "Hello C++"
> version = "0.1"
> license = "MIT"
> standard = "c++20"
> toolchain = "Clang"
>
> [target.main]
> # Refer to the target definition above
> # ...
>
> I am eager to receive any initial insights or feedback regarding this
proposed direction.
>
> [Your Name]
Received on 2026-01-29 17:36:18
