-
Notifications
You must be signed in to change notification settings - Fork 59
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
Bazelize plugin blog post #233
Comments
This is a great blog post. At this time, we are not adding externally authored posts to the Bazel Blog. This may change in the future and we will let you know. In the meantime, if you send me a link to a tweet about this blog post, I am happy to signal boost it by retweeting it from the Bazel twitter account. |
@hicksjoseph thanks for taking a look, I will have a link to share with you soon. Should this PR remain open for the future if the blog starts accepting externally authored posts? |
Let's close this PR for now. We can reopen it if we begin to accept externally authored posts. |
@hicksjoseph thanks, i've closed that PR. here's a link to the tweet https://twitter.com/codethink/status/1296432286045536257?s=20 |
Retweeted. Thanks. |
Hi, myself and some others at Codethink have been working on improving interaction between Bazel and BuildStream. As part of this there is a new kind of element plugin for Buildstream (bazelize) which can provide some level of automatic Bazel packaging for BuildStream projects.
I've written a blog post describing how this plugin can be used to integrate third party packages into existing Bazel projects. I think this will be of interest to other Bazel users so I'd like to send it as a PR here.
The text was updated successfully, but these errors were encountered: