feat: Make it easier to specify target architecture

[winksaville]

Create aliases build-arm run-arm build-riscv and run-riscv in
.cargo/config.toml. With these defined you can now use the alias which
will be converted to the full target name:

  cargo build-arm   -> cargo build --target thumbv8m.main-none-eabihf
  cargo run-arm     -> cargo run --target thumbv8m.main-none-eabihf
  cargo build-riscv -> cargo build --target riscv32imac-unknown-none-elf
  cargo run-risv    -> cargo run --target riscv32imac-unknown-none-elf

Append --release parameter to do release builds and runs. For example:

  cargo run-riscv --release ->
         cargo run --target riscv32imac-unknown-none-elf --release

feat: Make it easier to specify target architecture

Create aliases build-arm run-arm build-riscv and run-riscv in .cargo/config.toml. With these defined you can now use the alias which will be converted to the full target name:

cargo build-arm --bin blinky ->
cargo build --bin blinky --target=thumbv8m.main-none-eabihf
cargo run-arm --bin blinky ->
cargo run --bin blinky --target=thumbv8m.main-none-eabihf
cargo build-riscv --bin blinky ->
cargo build --bin blinky --target=riscv32imac-unknown-none-elf
cargo run-risv --bin blinky ->
cargo run --bin blinky --target=riscv32imac-unknown-none-elf

Append --release parameter to do release builds and runs. For example:

cargo run-risv --bin blinky --release ->
cargo run --bin blinky --target=thumbv8m.main-none-eabihf --release

[thejpster]

Nice idea. Can you put these in the README too?

[thejpster]

I'm not sure the extra aliases help with clarity. I was OK with the previous list of four:

build-arm = "build --target=thumbv8m.main-none-eabihf"
run-arm = "run --target=thumbv8m.main-none-eabihf"
build-riscv = "build --target=riscv32imac-unknown-none-elf"
run-riscv = "run --target=riscv32imac-unknown-none-elf"

Mainly because this saves you from typing the target name out in full.

Users are welcome to configure their personal projects however they wish. However, this is example code and a lengthy explaination of the short-form custom aliases (like rda) added here appears to me to detract from the purpose of helping them understand how to write and build code for RP2040 and RP2350.

[winksaville]

I'm not sure the extra aliases help with clarity. I was OK with the previous list of four:

build-arm = "build --target=thumbv8m.main-none-eabihf"
run-arm = "run --target=thumbv8m.main-none-eabihf"
build-riscv = "build --target=riscv32imac-unknown-none-elf"
run-riscv = "run --target=riscv32imac-unknown-none-elf"

Mainly because this saves you from typing the target name out in full.

Users are welcome to configure their personal projects however they wish. However, this is example code and a lengthy explaination of the short-form custom aliases (like rda) added here appears to me to detract from the purpose of helping them understand how to write and build code for RP2040 and RP2350.

Makes sense, but how about adding rra and rrb? I think those are the most useful and provide a hint at customization a user could do.

Do you like the build-xxx or bld-xxx?

[winksaville]

Txs for the feed back!

[thejpster]

I prefer build-xxx.

I think cargo run-arm --release is fine and doesn't need a short-hand.

[winksaville]

I prefer build-xxx.

SG

I think cargo run-arm --release is fine and doesn't need a short-hand.

Do you want me to keep rrr or delete that too?

[thejpster]

Delete that one - cargo run-riscv --release is fine.

[thejpster]

This is definitely heading in the right direction. Made a few suggestions.

[winksaville]

LGTM, txs the final tweaks!!!!

[winksaville]

Bravo, txs @9names and @thejpster for all the help and guidance!