https://github.com/sluongng/buck2-go

testing how buck2 would work with Go
https://github.com/sluongng/buck2-go

Last synced: 3 months ago
JSON representation

testing how buck2 would work with Go

• Host: GitHub
• URL: https://github.com/sluongng/buck2-go
• Owner: sluongng
• Created: 2023-05-03T10:13:45.000Z (over 1 year ago)
• Default Branch: master
• Last Pushed: 2023-07-10T10:21:35.000Z (over 1 year ago)
• Last Synced: 2024-05-21T12:04:52.666Z (6 months ago)
• Language: Starlark
• Size: 211 KB
• Stars: 4
• Watchers: 3
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-buck2 - buck2-go

README

        
# buck2-go

Buck2 build rules for Go

## Why?

This repository aims to be the equivalent of [bazelbuild/rules_go](https://github.com/bazelbuild/rules_go) for Buck2 ecosystem.

The eventual goal is to merge most of these rules back into Buck2 prelude.

Buck2 does come with some basic Go build rules under `prelude//go/...`, however they don't work outside of Meta (i.e. there is no stdlib to compile against).

It seems like the Go rules in Buck2 are also not maintained by anyone currently within Meta.

For faster iteration, let's work from a separate repo(this one) for the time being.

## Roadmap:

- [X] Remote Go Toolchain

  + [X] Fetch toolchain

  + [X] Export sub targets

  + [ ] Rework Go toolchain (GoSDK)'s provider

- [X] Build `go_bootstrap_binary` (same as `go_tool_binary` in Bazel)

  + [X] Implement `builder` binary

- [ ] Write Go Context

- [ ] Build Stdlib

- [ ] Write actions using `builder` binary

  + [ ] compilepkg

  + [ ] link

  + [ ] pack

  + [ ] archive

  + [ ] generate test source

- [ ] Write rules using actions

  + [ ] binary

  + [ ] test internal

  + [ ] test external

- [ ] Support 3rd party libraries

- [ ] Support CGO

- [ ] BXL

  + [ ] Go Package Driver + gopls

  + [ ] Linter

- [ ] Seperate host/exec/target platforms (transition?)

## Open questions

1. Extends Gazelle or write something new to support Buck2? (there is no repository loading phase)