Closed boozook closed 3 months ago
@boozook sorry for another noobish question/issue, I'd appreciate a nudge in the right direction. I tried updating my project's dependencies to point at playdate = { git = "https://github.com/boozook/playdate.git", branch = "dev/meta-assets" }
, as well as manually updating playdate-tool and playdate-bindgen:
cargo install --git https://github.com/boozook/playdate.git --branch dev/meta-assets playdate-tool
cargo install --git https://github.com/boozook/playdate.git --branch dev/meta-assets playdate-bindgen
@paulstraw,
I tried updating my project's dependencies to point at
playdate = { git = "https://github.com/boozook/playdate.git", branch = "dev/meta-assets" }
, as well as manually updating playdate-tool and playdate-bindgen
That's not needed. Here is just not-ready (but seems nothing is broken) version of cargo-playdate
cargo plugin in this PR. I'm still working on this.
So you're only interested in the cargo-playdate
tool in this brunch.
I recommend use API-crates such as playdate
, playdate-sys
, playdate-sound
,.. from the crates.io.
error: [package.metadata.playdate] not found in the manifest file Cargo.toml
Hmmmm, and now I'm not sure that nothing is broken 🤔 Thanks, I'll try to reproduce.
@paulstraw I don't think that's possible 🤯.
However, I still seem to be missing some part of the update, as builds give the enclosed error.
Packaging (single-target) pd3d:01_text_2d (source: dylib, target: dylib) error: [package.metadata.playdate] not found in the manifest file Cargo.toml
Are you sure that using this version of cargo-playdate
?
I'm absolutely sure in it because I've deleted (here) that error in this pre1
version.
But anyway I found that asset-dependencies are not works properly (#372).
@paulstraw Oh, seems I'v got it. May be you used one of previous commits where it still was. Fixed now.
Thanks for clarifying. After a cargo install --git https://github.com/boozook/playdate.git --branch dev/meta-assets cargo-playdate
locally, this is working for me as expected. I tried both the [package.metadata.playdate.example.my_example]
and [[package.metadata.playdate.example]]
+ target
versions, and got the expected results both ways.
Good, thank you.
Also I suppose there could be [package.metadata.playdate.assets.options]
? That is a breaking change, from now please use options.assets
instead of assets.options
.
playdate-build
:cargo-playdate
:cargo-playdate
refactoring 🥵playdate-build
⚠️ Breaking changes:
[package.metadata.playdate.assets.options]
not supported from now, useplaydate.options.assets