Skip to content
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

Allow specifying binary BEP in another location than /tmp/bep.bep #14

Open
2 tasks
jerrymarino opened this issue Dec 5, 2019 · 0 comments
Open
2 tasks

Comments

@jerrymarino
Copy link
Owner

The BazelBuildService example currently requires hardcoding by adding the param to their project's .bazelrc or ~/.bazelrc and it doesn't support multiple bazel builds at a time.

It needs more effort to set the param and or run Bazel directly. This is a good time to consider core features including:

  • Calling Bazel directly from here and dropping XCBuild's logic. Users currently have a runscript phase that invoke Bazel. Currently Tulsi and XCHammer both pass a temp JSON BEP path to Bazel.

  • BEP vs build event service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant