Alex
Found [this - rust-analyzer #14722](https://github.com/rust-lang/rust-analyzer/issues/14722).
Finally I've got it. It's not a `playdate-sys`, but `cargo-playdate` corrupts cargo's cache when planning units compilation. Trying to fix it... 🥵
I mean that main problem is in the `cargo-playdate`, but `playdate-sys` has build-script that also need a "tuning".
_Have been closed automatically by a mention._ @jcornaz, @notpeter, This issue is partially fixed in #385. Now `cargo-playdate` doesn't corrupts cargo's cache, so incremental build works now normally. And so...
Well, now `playdate-sys` causes cargo to rebuild __only__ when there is no pre-generated bindings and/or bindgen feature. Also now `cargo-playdate` respects cargo's cache and so doesn't corrupts incremental builds. Also...
Not sure why that needed in current state. Most of tools here uses SDK and/or Rust/LLVM toolchain, so you're need "full setup" almost anyway. I've created #227 just to speed...
Okay, I've made it in the #262 and previously #231. No prereleases, just artefacts attached to workflow-run, [there for example](https://github.com/boozook/playdate/actions/runs/8534486264#Artifacts). All artefacts built with debug info and stored for 3...
Thank you for this huge work! I hope to see it in the upstream soon. ❤️🔥 I'll just put it here. If you need some easy & fast solution to...
Thanks! I totally agree. This should be fixed and mentioned in README before.
Как вариант для автоматизации постинга, предлагаю рассмотреть сервис https://ifttt.com/ Бесплатен. Может следить за одной соц-сетью и перепостить в другую. Может следить за коммитами и проч.