Output is target specific but does not go in target directory

[DavidHorton5339]

CycloneDX picks up target-specific dependencies (as it should).
So, I need to run it for each of the multiple targets my project supports. However, by default it puts the output from the different runs in the same file.
Build output goes in a target/<target triple>/release directory, so maybe the SBOM should go there too.
There does not seem to be an option to specify the output directory, which would allow me to direct the output to a target specific directory.
--override-filename does not allow a directory path to be included, which might have been a different solution.
I tried changing to the desired output directory and using --manifest-path to find Cargo.toml, but the output was produced in the same directory as --manifest-path, not in the directory in which the tool was run.
I can specify --target-in-filename to provide disambiguation, so this is not a blocking issue.

[Shnatsel]

We don't write into the target/ directory deliberately, to avoid naming collisions within a single build. --target-in-filename is designed specifically to serve your use case.

Cargo is changing its target directory layout in a way that would prevent such collisions, so once that's done we could actually write SBOMs there: rust-lang/cargo#15010