CMD

@Flatout73 You only need the Pico SDK develop branch for RISC-V mode on the new RP2350. What you’ll (also) need regardless of platform is to change the `CMakeLists.txt` to [this](https://github.com/apple/swift-embedded-examples/issues/59#issuecomment-2343265666)...

As I previously mentioned, this PR addresses #59. The Pico SDK examples resulted in build errors with the new 2.0.0 SDK due to the required compiler flags not being passed...

To be honest, I didn't know that much CMake either - I learned while writing this. Feedback is definitely welcome 😅👍

> if we weren't using a custom command. I was wondering why this was used, and I found this [here](https://github.com/swiftlang/swift/blob/9461af4c5af904e5c997ed281778d6a51f1c561a/docs/EmbeddedSwift/IntegratingWithSDKs.md): > Finally, we need to define the application's build rules...

I've looked into this a bit this weekend, and I was able to successfully compile this simple test program (I know it doesn't change the architecture based on the environment...

> Perfect might be the enemy of good here. Right, using the CMake native support turned out to be a bit harder than expected. Might still be possible, though. Perhaps...

> Agree with all that's being said, and I'll throw in that we do have a couple of existence proofs of using the CMake native Swift support, e.g. here ....

I closed this by mistake, sorry. I deleted my patch-1 branch by mistake.

Small reminder that this still requires a Pico SDK update in order to run on the RISC-V cores (the patch is in the development branch, should release with 2.0.1). So...

> Any idea when the Pico SDK 2.0.1 will be released? I'm not sure... > agreed - this would save developers some headaches Done, what do you think?