Announcing Rust 1.18

Re:Announcing Rust 1.18 by vvanders on Thursday June 08, 2017 @12:31PM (#14515273)

> Finally, Cargo now supports Haiku and Android!

Does this mean you can now build Android targets without a standalone NDK? That part wasn't quite clear from the PR.

[ Parent | on HN ]

Re:Announcing Rust 1.18 by steveklabnik on Thursday June 08, 2017 @12:33PM (#14515281)

Cargo now runs on an Android host. I'm not an Android dev so I don't know what that means regarding the NDK.

https://github.com/rust-lang/cargo/pull/3885/files#diff-27a1... would imply to me that oyu still need an NDK.

[ Parent | on HN ]

Re:Announcing Rust 1.18 by vvanders on Thursday June 08, 2017 @12:36PM (#14515304)

Ah, gotcha.

Yeah, the Standalone NDK is a bit of a pain since the .cargo/config requires absolute paths to the linker/ar. It makes it hard to commit a common config file for multiple people working in one repo.

[ Parent | on HN ]

Re:Announcing Rust 1.18 by floatboth on Thursday June 08, 2017 @12:50PM (#14515392)

I use a build script that takes environment variables https://github.com/myfreeweb/freepass/blob/706e8d9f25f08ac34... (and calls Cargo once per architecture. Android has many :D)

[ Parent | on HN ]

Re:Announcing Rust 1.18 by anonova on Thursday June 08, 2017 @12:43PM (#14515346)

I use the executable name in the config and tell people to add $STANDALONE_NDK/bin to $PATH.

  [target.arm-linux-androideabi]
  ar = "arm-linux-androideabi-ar"
  linker = "arm-linux-androideabi-gcc"

[ Parent | on HN ]

Re:Announcing Rust 1.18 by vvanders on Thursday June 08, 2017 @12:45PM (#14515360)

Yeah, it'd be cleaner if you could include env vars in the config since I'm not a huge fan of polluting my PATH and usually NDK_HOME or similar is already defined.

[ Parent | on HN ]