Why Rust in Android will use the Soong build system, not Cargo

Re:Why Rust in Android will use the Soong build system, not ... by slezyr on Thursday May 13, 2021 @07:00AM (#27140733)

It seems that Google has more build systems that messengers: GN, Bazel, Soong, there were few more but I can not remember them.

[ Parent | on HN ]

Re:Why Rust in Android will use the Soong build system, not ... by gwmnxnp_516a on Thursday May 13, 2021 @11:07AM (#27142934)

At least Rust has far less building systems than C and C++ building system jungle: C, GNU Make, BSD Make, Windows Make, GNU autotools, and much more. Google may have a valid reason for not using Cargo, since they may need to integrate Rust with existing C and C++ code. It would be nice if Cargo had a way to build and link C and C++ dependencies in the same source tree as there are many C libraries which the functionality is still missing in Rust.

[ Parent | on HN ]

Re:Why Rust in Android will use the Soong build system, not ... by gutino on Thursday May 13, 2021 @09:31AM (#27141851)

Ninja! used in chrome/v8 https://en.wikipedia.org/wiki/Ninja_(build_system)

[ Parent | on HN ]

Re:Why Rust in Android will use the Soong build system, not ... by slezyr on Thursday May 13, 2021 @09:40AM (#27141939)

I think that ninja is fine, but I was wrong with the terms. All those are build automation tools[1] and ninja is a build system. Also, that article refers to GYP[2] yet another build automation tool from Google.

1: https://en.wikipedia.org/wiki/Build_automation

2: https://en.wikipedia.org/wiki/GYP_(software)

[ Parent | on HN ]