output configured targets

[Emilgardis]

$ cross-util list-targets --format-version=1
{
  "format_version": "1",
  "targets": [
    {
      "platforms": [
        "linux/amd64=x86_64-unknown-linux-gnu"
      ],
      "triplet": "x86_64-unknown-linux-gnu"
    },
    {
      "platforms": [
        "linux/amd64=x86_64-unknown-linux-gnu"
      ],
      "triplet": "x86_64-unknown-linux-musl"
    }
	<...snip...>
  ]
}

[Emilgardis]

@mcandre does this work for you? I can add more data to the array

[Emilgardis]

this is a nice usage of try trait :D

[Emilgardis]

Suggested change

	triplet: Some(i.name).filter(|i| *i != "zig")?.to_owned(),
	triplet: if *i.name != "zig" { i.name.to_owned() } else { return None },

[Emilgardis]

this is meant to replicate what happens when we do https://github.com/Emilgardis/cross/blob/list-supported-targets/src/docker/image.rs#L30

[Emilgardis]

should there be a way to only output targets in toml config? Maybe that could be data included in the output?

[Emilgardis]

do we really need this kind of stability?

[mcandre]

@mcandre does this work for you? I can add more data to the array

For my purposes, I would like to see the support tier number included in the output. Perhaps a field like "support_tier": 3 as a sister field beside the "triplet" fields.

If possible, I would prefer a flatter array design, that doesn't restate some of the triple and platform information. I just want to be able to associate triple with support tier number.

If we go with JSON, then I would like to see all cross data models exported as a stable Rust library. The current policy treats only the CLI as stable. Until the data models and schemas (e.g., the entire Cross.toml schema) enter a stable library, I would actually prefer to see non-JSON in cross CLI tool output.

That is, docker ps -a-style text tables would be fine. These are easier to parse through via simple regex captures, than a long series of manual JSON value casting and checking snippets.

[Emilgardis]

For my purposes, I would like to see the support tier number included in the output. Perhaps a field like "support_tier": 3 as a sister field beside the "triplet" fields.

The tier is not relevant to cross, all targets emitted are the targets that actually has been setup for the project. i.e not every tier 1 and tier 2 target are emitted, only targets in any tier, including custom targets when specified in a projects config, are emitted iff they are supported by cross or have been setup to work with cross in the project which cross-util has been executed from.

i.e

# Cross.toml
[target."my-custom-target.json"]
image = "my-image:latest"
build-std = false

[target.aarch64-apple-ios]
image = "aarch64-apple-ios-cross:local"

would output with cross-util list-targets --format-version=1 that the targets my-custom-target.json and aarch64-apple-ios are a target. See https://docs.rust-embedded.org/embedonomicon/custom-target.html

If we go with JSON, then I would like to see all cross data models exported as a stable Rust library. The current policy treats only the CLI as stable. Until the data models and schemas (e.g., the entire Cross.toml schema) enter a stable library, I would actually prefer to see non-JSON in cross CLI tool output.

That's the entire reason behind --format-version 1, we are guaranteeing that if you use --format-version 1 you'll get the same object/schema.