Hi Geguji, I would recommend to you to contact René Ferdinand, Ben Craig and Matthew Woehlke   See also:   https://cps-org.github.io/cps/ which is now also somewhat supported by CMake https://www.kitware.com/navigating-cmake-dependencies-with-cps/     The build configuration is not the actual C++ language. So there will be a bit more reluctance to put it into the standard. Especially if you create something new, it would probably need broad support of different compilers or build systems. This is probably more important than the technical merits.   The mentioned people above have been working on this topic for quite some time and could be of more help than me, I think.     -----Ursprüngliche Nachricht----- Von:geguji60_at_[hidden] Gesendet:Fr 23.01.2026 14:38 Betreff:Re: AW: [std-proposals] The C plusplus package manage and build tool proposal An:Sebastian Wittmeier <wittmeier_at_[hidden]>; CC:std-proposals <std-proposals_at_[hidden]>; Hi, Sebastian. I have never presented any facts to the group before. This is my first proposal. If you are willing to organize these, then I would greatly appreciate it, as it compensates for my introverted and difficult to express shortcomings. My general idea is to use toml as the standard build configuration file format for C++. Thank you very much. ---- Replied Message ---- From Sebastian Wittmeier<wittmeier_at_[hidden]> Date 01/23/2026 21:14 To std-proposals_at_[hidden] Cc geguji60_at_[hidden] Subject AW: [std-proposals] The C plusplus package manage and build tool proposal 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_at_[hidden] <mailto:std-proposals_at_[hidden]> > Gesendet:Fr 23.01.2026 14:17 Betreff:[std-proposals] The C plusplus package manage and build tool proposal An:std-proposals <std-proposals_at_[hidden] <mailto:std-proposals_at_[hidden]> >; CC:geguji60_at_[hidden] <mailto:geguji60_at_[hidden]> ; 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_at_[hidden] <mailto:Std-Proposals_at_[hidden]> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals