Skip to content

Do not declare bash output on windows#1262

Merged
vladmos merged 2 commits intobazelbuild:masterfrom
limdor:patch-1
Apr 12, 2024
Merged

Do not declare bash output on windows#1262
vladmos merged 2 commits intobazelbuild:masterfrom
limdor:patch-1

Conversation

@limdor
Copy link
Contributor

@limdor limdor commented Apr 7, 2024

Calling declare_file on windows even if later is overwritten is a problem in windows genereting the following error

The following files have no generating action:
buildifier.bash

Calling declare_file on windows even if later is overwritten is a problem in windows genereting the following error
```
The following files have no generating action:
buildifier.bash
```
fail("Cannot use 'no_sandbox' without a 'workspace'")
workspace = ctx.file.workspace.path

out_file = ctx.actions.declare_file(ctx.label.name + ".bash")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

@vladmos vladmos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@vladmos vladmos merged commit f077f7a into bazelbuild:master Apr 12, 2024
apattidb pushed a commit to databricks/buildtools that referenced this pull request May 10, 2024
Calling declare_file on windows even if later is overwritten is a problem in windows genereting the following error
```
The following files have no generating action:
buildifier.bash
```
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

Successfully merging this pull request may close these issues.

2 participants