Re:Rust and C++ Interoperability in Chrome
by Rochus on Wednesday August 19, 2020 @01:51PM
(#24213515)
So building Chromium becomes even more complex. Understanding the build system alone is a major achievement; I even had to build a tool for that: https://github.com/rochus-keller/gntools/. Unfortunately that's only half of the rent; it also needs hundereds of Python scripts; and now also crates will be added.
[ Parent
| on HN ]
Re:Rust and C++ Interoperability in Chrome
by malkia on Wednesday August 19, 2020 @06:06PM
(#24217282)
Fuchsia, uses also "gn" (then ninja) and has rust support too
Re:Rust and C++ Interoperability in Chrome
by staticassertion on Thursday August 20, 2020 @01:36AM
(#24220226)
The post is how they are not using rust, how could you possibly have come to the conclusion that the builds are going to get more complicated?
Re:Rust and C++ Interoperability in Chrome
by ComputerGuru on Thursday August 20, 2020 @04:34AM
(#24221176)
Because they’re clearly interested in possibly doing so in the future?
Re:Rust and C++ Interoperability in Chrome
by bitwize on Wednesday August 19, 2020 @09:13PM
(#24218839)
> So building Chromium becomes even more complex.
Suck it up and get used to it. Rust is absolutely the future of systems development; every major C or C++ project -- including the kernel -- is going to have a Rust interoperability story, and eventually, major components that implement desirable features written entirely in Rust, so in the interim, until the desirable but currently unrealistic goal of migrating all extant C and C++ code to Rust is achieved, you will need to have both C(++) and Rust tooling (and whatever else) to build the project.