Using Go (or Python or whatever) for this implies either the build system needs to include compiled binaries (not good) or the system doing the build needs to have a Go (or xyz) interpreter installed. So cross-platform build configurations will require an external dependency (or writing separate scripts for each target platform) if external scripts are used.
On Tuesday 24 Jun 2014 16:56:31 John Mija wrote: > El 24/06/14 12:05, Huon Wilson escribió: > > On 24/06/14 20:41, György Andrasek wrote: > >> The FAQ says: > >> > Our solution: Cargo allows a package to specify a script to run > >> > >> before invoking |rustc|. We plan to add support for platform-specific > >> configuration, so you can use |make| on Linux and |cmake| on BSD, for > >> example. > >> > >> Just to make it perfectly clear, this will force a Cygwin dependency > >> on cargo in practice. One popular package using autotools is enough to > >> make it mandatory. Is this a conscious tradeoff? > > > > Just to be clear: what's the trade-off here? That is, what is the > > alternative: not supporting running external scripts at all? > > You don't need a Cygwin dependency if you use Go for this task. > It's a simple language, multi-platform and with binary distribution for > systems most used (Windows, Mac OS X, Linux). > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
