Announcing Rust 1.23

Re:Announcing Rust 1.23 by RazrFalcon on Thursday January 04, 2018 @04:14PM (#16074157)

If we are talking about C++ then the problem is that there a too many build systems and all of them are incompatible.

CMake is quite popular (and maybe most popular) but it's a complete horror in comparison to other build systems, especially for other languages (like Cargo for Rust).

If you need some specific example: try to add a git-based dependency with a specific branch in CMake.

[ Parent | on HN ]

Re:Announcing Rust 1.23 by pjmlp on Friday January 05, 2018 @02:57AM (#16077250)

Build systems should be agnostic from source control systems.

The unit of dependencies should be other projects or binary libraries.

[ Parent | on HN ]

Re:Announcing Rust 1.23 by qznc on Friday January 05, 2018 @11:09AM (#16079423)

I'm not sure about that. If you have dependencies to other internal repositories and to specific revisions, it is not clear who is responsible. Make can be agnostic, but Maven or NPM probably can not.

[ Parent | on HN ]

Re:Announcing Rust 1.23 by pjmlp on Friday January 05, 2018 @12:28PM (#16079991)

Maven surely can. You only depend on binary versions of Java libraries, no source code, as it should be.

[ Parent | on HN ]

Re:Announcing Rust 1.23 by qznc on Thursday January 04, 2018 @07:01PM (#16075290)

My first idea would be to use git-submodule and keep CMake ignorant of that.

[ Parent | on HN ]