-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial bazel support #3510
Initial bazel support #3510
Conversation
cc @chrislovecnm and @alrs ... it's alive :-) |
WAHOO ... The 1.8 version bump is in the merge queue now |
we will need the hack scripts for maintaining and validating the bazel files. Will create issue. |
Congrats! |
Still lots of work needed ... this is really just the bare minimum. But rebased so should be cleaner now. Second commit is all autogen, first commit is the interesting stuff. |
Can we rebase and get this in? Would like to start adding some TLC with hack files and such. |
It is rebased @chrislovecnm ... |
/lgmt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not going to review 3k files. Let's get this in :P
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrislovecnm The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Builds on the 1.8 version bump
The "trick" is to strip the BUILD & BUILD.bazel files from the vendor-ed deps.
Will rebase after 1.8 version bump merges.