Expand description
The Playdate exporter (ADR-0062): the game’s library built as a static
library for the device (thumbv7em-none-eabihf) and, on Windows where
MinGW is at hand, for the Simulator (x86_64-pc-windows-gnu), linked with
the backend’s C shim and the SDK’s setup.c; its pack and its sounds and
music (audio) baked beside them, its pdxinfo and launcher images
written and NOTICES.txt; all packed by
the SDK’s pdc into <base>.pdx, and zipped for sideloading.
The export is a list of Steps (plan), so the tests check every
command without the SDK; export runs them.
Modules§
- audio
- The Playdate’s sounds and music, baked for
pdc: every sound file of the audio the game ships there, and each of its music tracks, decoded (OGG Vorbis or WAV), mixed down to mono and written as an IMA ADPCM WAV at its own 44.1 kHz, underBAKED_SOUND_DIRandBAKED_MUSIC_DIR, whereshuyi-playdateopens them.pdcturns each into a.pda.
Structs§
- Dirs
- The folders of a build.
- Playdate
Exporter - The Playdate exporter’s type.
- Tools
- What the build needs from the machine.
Enums§
- Step
- One thing the export does.
Constants§
- DEVICE
- The device’s Rust target.
- FEATURE
- The cargo feature of a game’s package that makes its library the game on the Playdate.
- SIMULATOR
- The Simulator’s Rust target: MinGW, like the GNU host toolchain.
Statics§
- PLAYDATE
- The Playdate exporter.
Functions§
- find_
sdk - The first of
candidatesthat holds an SDK (itsC_API/pd_api.h), or how to install one. - pdxinfo
- The
pdxinfoof the gamepartsays, atversion, with the launcher’s images in its launcher folder if it has any. - plan
- The steps of
cx’s export, withtools, intopdx. - playdate_
pack - The pack’s file in the
.pdx, asshuyi-playdatereads it: a test keeps the two equal. - sdk_
candidates - Where to look for the SDK, in order:
PLAYDATE_SDK_PATH, then~/Documents/PlaydateSDK(the installer’s default).