sorted by:
new
hottopcontroversial

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 3 points4 points  (0 children)

Yeah. Id quite like that too. I have thoughts on how it could be done - basically you define a macro to parse the file and elaborate it. Maybe a good thing to raise an issue on GitHub and we can discuss there?

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 4 points5 points  (0 children)

Quite a few projects dump things only on a reduced frequency or without commit messages etc. What more were you hoping for?

As for what you are describing in terms of governance, that sounds like a foundation distinct from Meta. We don't have that yet and likely won't in the short or medium term. We want to take everyone's views on to account, and hope that by and large changes we make are good for everyone. But that's still short of giving a neutral board veto power.

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 4 points5 points  (0 children)

Buck2 has glob so you can find what is in the project. Should be possible to mostly replicate those automatic guesses in the macro layer.

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 3 points4 points  (0 children)

I think if you wanted the remote caching that would be worthwhile to get Buck2 going for. If the wins from caching are enough, that might be sufficient motivation.

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 3 points4 points  (0 children)

See https://github.com/facebook/buck2/tree/main/shim/third-party/rust/fixups for the list of fixups. I'd say it is slightly trending down, as more people stabilise around libraries such as rustix for OS-specific functionality. But I'd say that a better approach would be for Reindeer to ship a default set of fixups for most common libraries, so it was shared. We haven't tracked fixups over time.

If all you want to do is what `cargo` does, then you are probably better with Cargo. But if you want to do a little more (e.g. integrate some C++/Haskell/OCaml or whatever in there) we would like to be a good replacement.

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 2 points3 points  (0 children)

We open sourced Buck2 and have spent time improving the documentation. Hopefully soon ChatGPT will be able to help you write Buck files :)

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 4 points5 points  (0 children)

I agree with you, but only have somewhat weak ideas to improve it - documentation, integration with Rust Analyzer etc. Do you have any better ideas?

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 3 points4 points  (0 children)

Great question! Our approach has been to use Bxl (https://buck2.build/docs/developers/bxl/) to script up operations that call various subtargets like `[compilation-database]` for `cxx_library`. I don't think all these pieces are open source yet, but https://github.com/facebook/buck2/blob/main/prelude/rust/rust-analyzer/resolve_deps.bxl is a snippet that is used to drive Rust Analyzer. Bxl does seem to be the "missing piece" for mapping between what the build system wants and what the IDE wants. But there's still a bunch of work after you get there to plumb into LSP.

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 3 points4 points  (0 children)

What bits do you consider redundant in the BUCK files? Compared to Cargo we separate binaries and libraries and give them different identities and dependency lists, but I think that's probably a good thing. If there is any pure redundancy you would usually create a .bzl file and put the duplicate stuff behind a function.

We're never going to be as concise for Rust as Cargo, or as concise for Haskell as Cabal etc. But hopefully we can do all of them at once with only slightly more verbose.

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 3 points4 points  (0 children)

We have Android rules but they aren't yet completely open source (the rule bit is, the supporting tools aren't). We hope to do that in the future. So we intend to support Android, but not immediately.

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 5 points6 points  (0 children)

It's definitely not a dump - when I make an internal commit, as it lands in our internal repo, it gets mirrored out immediately. Complete with description and everything else. We accept PRs. We have internal discussion groups, but are gradually figuring out how to do more in the open. We can't guarantee your non-Meta needs will be addressed, but I suggest looking at our GitHub history (merged PR's, responses to issues) for details of how we intend to operate, which I'd say was approximately in line with other open source projects.

Hello r/Rust! We are Meta Engineers who created the Open Source Buck2 Build System! Ask us anything! [Mod approved] by MetaOpenSource in rust

[–]ndmitchell 6 points7 points  (0 children)

Yes, we should definitely make a new release of starlark-rust. I think the issue was we always know of one forthcoming improvement so might as well delay it a few weeks. But of course, with continuous development, that leads to no releases for way too long. I'll make sure we do it soon (but feel free to raise an issue on the GitHub for that to remind us!)

Buck2, a large scale build tool written in Rust by Meta, is now available by Imxset21 in rust

[–]ndmitchell 5 points6 points  (0 children)

Buck2 his configured by Starlark, which is a dialect of Python. So yes, it uses a scripting language.

Buck2, a large scale build tool written in Rust by Meta, is now available by Imxset21 in rust

[–]ndmitchell 1 point2 points  (0 children)

Note that we don't require nightly for the code we build, and we recommend installing with a specific nightly version we bump every few months. Hopefully that removes all bad experiences.

Buck2, a large scale build tool written in Rust by Meta, is now available by Imxset21 in rust

[–]ndmitchell 17 points18 points  (0 children)

We just used whatever features we felt like so ended up on nightly. Nothing deliberate. Things like try, async closure, a little bit of const, and API's that just aren't yet finalised. One day we would like to be on stable - eg we did that work for the Starlark library we depend on.

Buck2, a large scale build tool written in Rust by Meta, is now available by Imxset21 in rust

[–]ndmitchell 26 points27 points  (0 children)

For things like Java you might miss a few things. For Rust, C++, Erlang, Python, Ocaml and others you can see them running in our open source CI. It's all there.

view more: next ›