> 
Hello all,

The Cuthour <cuth...@gmail.com> wrote to the GCC mailing list

> I understand that GNU Make and C++ Modules address many current challenges
> with headers and dependency management.
> 
> But what I'm suggesting is a build+package manager tightly integrated with the
> compiler — something like Rust's cargo, which not only handles builds and
> dependencies, but also allows:
> 
>   - No headers, no macros
> 
>   - Cache-aware recompilation (template & inline function tracking)
> 
>   - Consistent ABI output per toolchain (e.g., Rust ABI, Go ABI)
> 
>   - Per-project manifest with proper dependency/version resolution
> 
> 
> Would the GCC project consider supporting such a tool if developed
> independently as cargo-cc? It could be a frontend to g++, like rustc is for
> Rust, but standardized.


Most people don't need it, since the GNU project offers other (old) approaches
(e.g. GNU autoconf and GNU automake).

My suggestion is not to incorporate that feature into the GCC compiler, but for
The Cuthour to implement it first as an open source (probably GPL licensed) GCC
plugin. People would then chose to use (or not) it.


Perhaps some of the old (unmaintained, somehow obsolete) code on
https://github.com/bstarynk/bismon could then be useful to you (I don't maintain
that code anymore).

http://www.starynkevitch.net/Basile/bismon-chariot-doc.pdf contain some old
documentation.

BTW my current free software project is on refpersys.org (a GPL licensed
inference engine for Linux). 
Its C++ code (compiled by GCC) being on github (see my signature).


Regards from near Paris in France.
-- 
Basile STARYNKEVITCH                            <bas...@starynkevitch.net>
8 rue de la Faïencerie                       http://starynkevitch.net/Basile/  
92340 Bourg-la-Reine                         https://github.com/bstarynk
France                                https://github.com/RefPerSys/RefPerSys

Reply via email to