[rust-dev] RFC: Future of the Build System

George Makrydakis irrequietus at gmail.com
Sat Jan 11 08:53:54 PST 2014

I would not exclude ninja from the candidates of an in - between solution
for the time being. Imagine the power of ninja but implementing its
conceptual machinery in expressive Rust code. It would be an interesting
combination indeed. That could bring even more advantages since it would be
implemented in Rust.

On Sat, Jan 11, 2014 at 2:03 PM, james <james at mansionfamily.plus.com> wrote:

> On 10/01/2014 08:54, Jan Niklas Hasse wrote:
>> Also cmake still depends on make (or even worse Visual Studio / Xcode).
> We use cmake with ninja at work, and that seems to work pretty well.
> I suggest if you want to write a tool, then you first write something that
> generates ninja files.  Then you immediately have a bootstrap mechanism,
> plus something that will do builds rather quickly thereafter.  scons can be
> (very) slow.  My experience with waf was better, but I think generating a
> nnja script is superior and there are several tools to do that.  You could
> look at gyp, for example.
> _______________________________________________
> Rust-dev mailing list
> Rust-dev at mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/rust-dev/attachments/20140111/49b632b2/attachment.html>

More information about the Rust-dev mailing list