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.

Sign up for GitHub

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

Jump to bottom

String 'blaze' appears in install_base and execution_root #26

Closed
alexeagle opened this issue Mar 24, 2015 · 0 comments
Closed

String 'blaze' appears in install_base and execution_root #26

alexeagle opened this issue Mar 24, 2015 · 0 comments
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) type: bug

Comments

@alexeagle
Copy link
Contributor

$ ./output/bazel info execution_root
/private/var/tmp/_blaze_alexeagle/048dc339e919adf019cd498aa08795ff/bazel
@damienmg damienmg added type: bug P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) labels Mar 26, 2015
tomaszstrejczek pushed a commit to tomaszstrejczek/bazel that referenced this issue Oct 20, 2019
@pcj @zaphar
Adds new_nuget_package (bazelbuild#27)
f8950cb 
* - Adds new_http_archive for nuget-binary from github commit zipfile.
- Adds label attributes to nuget_package rule to get mono and nuget binary paths.
- Checks return value of execute nuget_cmd and fails with non-zero value.
- Changes dll_import rule in nuget_package BUILD from
  `@workspace_name//:workspace_name` to `@workspace_name//:dylibs`
  (less redundant, more descriptive).
- Bumps README.md to 0.0.3.

* - Adds new_nuget_package as workaround for Issue bazelbuild#18.
- csharp_binary fixes for path outputs. Closes bazelbuild#26.

* Reverts attr dict addition to maintain syntax conformance with python.

* Documentation for new_nuget_package.
@rock626 rock626 mentioned this issue Apr 29, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexeagle @damienmg