-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Generic --host_opt flag #13048
Copy link
Copy link
Open
Labels
P2We'll consider working on this in future. (Assignee optional)We'll consider working on this in future. (Assignee optional)not staleIssues or PRs that are inactive but not considered staleIssues or PRs that are inactive but not considered staleteam-Configurabilityplatforms, toolchains, cquery, select(), config transitionsplatforms, toolchains, cquery, select(), config transitionstype: feature request
Milestone
Metadata
Metadata
Assignees
Labels
P2We'll consider working on this in future. (Assignee optional)We'll consider working on this in future. (Assignee optional)not staleIssues or PRs that are inactive but not considered staleIssues or PRs that are inactive but not considered staleteam-Configurabilityplatforms, toolchains, cquery, select(), config transitionsplatforms, toolchains, cquery, select(), config transitionstype: feature request
One thing we see come up a lot is needing to pass options that we pass to our build differently for the host configuration. In some cases bazel has a flag for this like
--host_swiftcopt/--swiftcoptetc. In other cases, for whatever reason, bazel does not yet have a flag for the use case, such as #13001 or--host_featuresand how--featuresapplies everywhere.I think it would be useful for there to be a generic
--host_optflag with syntax such as--host_opt=--normal_opt=valuethat allowed you to pass through arbitrary bazel options to the host configuration.This opens the door for much more API usage for the host configuration, but I think that could be preferred to the trade off of trying to add a host flag for ever applicable option.