On Fri, Apr 25, 2025 at 6:34 AM Bruno Haible via Gnulib discussion list <bug-gnulib@gnu.org> wrote: > > Nikolaos Chatzikonstantinou wrote: > > > One problem I see with Rust is that currently it does not integrate well > > > with the GNU Build system, in particular with VPATH builds (see [3] for > > > an example integration). Any improvements on that front would be welcome. > > > > > > [3] > > > https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=tree;f=gettext-tools/examples/hello-rust;hb=HEAD > > > > What is the issue with VPATH builds? > > The issue is that 'cargo' mandates a certain directory layout of the > package, that is incompatible with VPATH builds. > > > I read the comments in > > configure.ac of that link, it seems to copy certain files into the > > build directory and then uses cargo. Would you rather if it used rustc > > directly? > > How can a package not use 'cargo' if it needs some Rust libraries? > > It's very much possible that I did not see/find some "obvious" solution, > though. > > > I can try to tackle support for Rust too. > > That would be welcome!
Another sharp edge with Rust is, sometimes it cannot build its own cargos. I experienced this problem when trying to port some Rust programs from x86_64 to arm, arm64, mips and powerpc. Also see Rust's Platform Support, <https://doc.rust-lang.org/beta/rustc/platform-support.html>. Tier 1 is expected to build and run correctly. Tier 1 is i686, x86_64 and some aarch64. Everything else, Tiers 2 & 3, are a best effort with no guarantees. [Sorry to post here. I cannot find the original message in my Inbox.] Jeff
