Alex

@ishche Seems to fixed, I can't reproduce with [`cargo-playdate v0.5.0-beta.6`](https://crates.io/crates/cargo-playdate/0.5.0-beta.6). Could you try it plz? You can install it with `cargo install [email protected]`. Could be awesome if you confirm that...

> `"img/system/" = "${PLAYDATE_SDK_PATH}/Examples/Game Template/Source/SystemAssets/*.png"` Is's a glob in the path. There is blocking wax's issue https://github.com/olson-sean-k/wax/issues/34 , but I'll try to workaround it translating paths to normal slash `/`...

Also, seems to current implementation works normally if run in the bash-like shell on windows, but not in powershell.

If you're using `cargo-playdate`, it causes because I have to fix inner cargo ctx configuration to _do not touch cache_ of your real cargo. If you're building just `playdate-sys` as...

@jcornaz, could you please try to build with `-vv` and tell me list of prints that contains `cargo:rerun-`?

Hm... probably my mistake in this two lines: ``` [playdate-sys 0.2.10] cargo:rerun-if-env-changed=TARGET [playdate-sys 0.2.10] cargo:rerun-if-env-changed=PROFILE ``` I'll try without it, by absolutely not sure. 🤷🏻‍♂️ Also I don't remember why...

I see this as table in `package.metadata.playdate.dev."{example-name}"` with same manifest fields as in main table, but all fields should be optional there. And I see consistency problem here. Look, we...

🤔 Let's say, okay. But here's another open question: One powerful `cargo-playdate` feature that may become main-killer-feature in the future is compiling optimized binaries without gcc. (`[[bin]]`) There can be...

Also I have issue about workspace metadata and inheritance like `package`-fields - #26.

@paulstraw, I'll do a little refactoring before. Because there is a lot of unnecessary stuff left there, e.g. for `cargo-metabuild` support and other currently unnecessary junk. That's easy and fast...