Closed libsamek closed 4 years ago
Stale issue message
Stale issue message
@achew22 I assume that ibazel has a limited number of flags which are non overlapping with bazel's flags. Perhaps you can just detect ibazel flags and if you encounter a flag that ibazel doesn't recognize forward it on to bazel
Stale issue message
Uugh, why can't I tag an issue as "definitely not stale" and have it linger?
Stale issue message
Hey folks, just wanted to check in on this. We want to use the --output_base
and --output_user_root
startup flags, but on my fork, it seems like they're being counted as ibazel
flags.
What did you modify in the fork?
I added the --profile=
and --run_script=
run flags to overridableBazelFlags
. I'm trying to add --output_base
and --output_user_root
, which are both startup flags, but I'm running into the same issue as @libsamek where these flags are being treated as ibazel
flags
Did you add them to the startup flag list?
Ah, I see now. You have to pass all flags (including startup flags) after the command.
You have to pass them after ibazel
, yes. Other than that there should be no restriction.
Currently ibazel arguments are the following:
Where
ibazel_flags
are internal ibazel specific arguments andbazel_flags
are actual Bazel flags. The issue with this can be with Bazel startup arguments, eg. --bazelrc, which is passed asibazel build --bazelrc=some-bazelrc //...
. It would be desired if we could do something likeibazel --bazelrc=some-bazelrc
to be consistent with Bazel arguments.But then again the question arises, how to handle ibazel arguments.