Is your feature request related to a problem? Please describe.
I'd like to use cargo-about to generate a THIRDPARTY flat file to be included with each target's nightly build at https://github.com/artichoke/nightly.
I would like to set the targets field in the about.toml to be limited to the single target triple used for each nightly build artifact.
The about.toml file is global per project, so I can only include one targets key.
Describe the solution you'd like
A command line flag which will allow me to customize which about.toml is used when invoking cargo-about:
cargo about generate --config ./windows/about.toml about.hbs
Describe alternatives you've considered
I attempted to execute cargo-about in a subdirectory with an alternative about.toml and use --manifest-path to point to the crate root. Unfortunately, cargo-about loads the about.toml relative to the directory containing the manifest rather than the cwd.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
I'd like to use
cargo-aboutto generate aTHIRDPARTYflat file to be included with each target's nightly build at https://github.com/artichoke/nightly.I would like to set the
targetsfield in theabout.tomlto be limited to the single target triple used for each nightly build artifact.The
about.tomlfile is global per project, so I can only include onetargetskey.Describe the solution you'd like
A command line flag which will allow me to customize which
about.tomlis used when invokingcargo-about:Describe alternatives you've considered
I attempted to execute
cargo-aboutin a subdirectory with an alternativeabout.tomland use--manifest-pathto point to the crate root. Unfortunately,cargo-aboutloads theabout.tomlrelative to the directory containing the manifest rather than the cwd.Additional context Add any other context or screenshots about the feature request here.