sailfish-sdklisted
Install: claude install-skill teekesti/sailfish-agent-skills
# Sailfish OS SDK (sfdk)
Sailfish apps link against `sailfishapp`/`Sailfish.Silica`, which only exist
inside the Sailfish SDK's target sysroots — the host's own `/usr` and system Qt
(if any) are a different, usually incompatible, build and must never be used
for building *or* for looking up source. All building, running, and testing
must go through `sfdk`; never invoke the host's own `qmake`/`g++` even if present.
## Locate the SDK and pick a target
The install path varies per machine — resolve it once per session, in order:
1. `$SAILFISH_SDK_HOME` environment variable, if the user has set one.
2. The common default `~/SailfishOS`.
3. Search for it: `find ~ -maxdepth 4 -name targets.xml -path '*/mersdk/*' 2>/dev/null`
(that file only exists inside a real SDK install). If still nothing, ask the user.
Keep the result in one variable and reuse it for everything below — don't
re-hardcode the path elsewhere:
```bash
SFDK_HOME=~/SailfishOS # replace with whatever step 1-3 found
SFDK="$SFDK_HOME/bin/sfdk"
```
Once located, worth saving as a reference memory so future sessions skip
re-discovery.
Key paths/executables inside it:
- `$SFDK` — the CLI frontend to the build engine. Use this for everything below.
- `$SFDK_HOME/mersdk/targets/targets.xml` — lists installed targets, e.g.
`SailfishOS-<version>-i486`, `-armv7hl`, `-aarch64`.
List targets and pick the `i486` (x86) one when the binary needs to run
*natively* on an x86_64 host (e.g. for tests) — it's the only arc