Date: Fri, 23 Jan 2026 14:23:42 +0100
https://imgs.xkcd.com/comics/standards_2x.png
On Fri, 23 Jan 2026 at 14:17, geguji60--- via Std-Proposals <
std-proposals_at_[hidden]> 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:
>
> 1. Target Definition:
>
> [target.main]
> flags = ["-O2"]
> src = ["src/main.cpp"]
> buildtype = "Release"
>
>
> 2. 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]
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
On Fri, 23 Jan 2026 at 14:17, geguji60--- via Std-Proposals <
std-proposals_at_[hidden]> 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:
>
> 1. Target Definition:
>
> [target.main]
> flags = ["-O2"]
> src = ["src/main.cpp"]
> buildtype = "Release"
>
>
> 2. 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]
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals
>
Received on 2026-01-23 13:23:59
