Hi Geguji,

this list is not the actual committee yet, but I assume you want feedback for giving such an input to the committee.

[Your Name] probably should be your name.

 

> Continuing from my previous communication

Have you made a proposal with a number or sent specific inputs to a sub-committee or a member? I would put in a better reference - than just mentioning that there had been communication before.

 

I remember there was a similar standardization being worked on by René Ferdinand Rivera Morell:

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3051r2.html (Structured Response Files)

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p2656r3.html (C++ Ecosystem International Standard)

and the withdrawn variants/updates

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3051r3.html

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p2656r4.html

 

Perhaps contact René Ferdinand about the topic and the reception and the possible hurdles for such an undertaking.


 

-----Ursprüngliche Nachricht-----
Von: geguji60--- via Std-Proposals <std-proposals@lists.isocpp.org>
Gesendet: Fr 23.01.2026 14:17
Betreff: [std-proposals] The C plusplus package manage and build tool proposal
An: std-proposals <std-proposals@lists.isocpp.org>;
CC: geguji60@163.com;

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"
  1. 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@lists.isocpp.org
 https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals