You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8e511f5
Browse filesBrowse the repository at this point in the historyBrowse files
dist-apk: read deployed assets from the staged tree, at plan time
Per docs/30 ("Producing a distributable") and e2e 651/649 in the mcpp
tree, `mcpp::deploy`'s `to` lands at `<staged tree>/bin/<to>/...`, and
the second pass of `mcpp pack --format apk` runs `plan_for` after the
tree is staged -- so, like every other member's own reads against
`pack_stage_dir()`, this member now enumerates `<stage>/bin` with
`std::filesystem::recursive_directory_iterator` in `plan_for` itself,
declares each file as an individual action input, and maps
`bin/<rel>` to `assets/<rel>`. The command-time helper that used to
scan `${mcpp.bin_dir}` for this is gone; `copy-then-jar.sh` now only
copies the archive and hands it to `jar`.
MEASURED REGRESSION, NOT HIDDEN: on `*-linux-android`, with this exact
engine build, the staged tree carries `lib/<name>.so` and NOTHING
ELSE -- `run_shared_program` (mcpp.pack) never calls
`stage_runtime_files`, unlike every other row's `run()` (see this
member's header). So the loop above is correct against the documented
contract and is a no-op on THIS row today: `apk-consumer`'s deployed
`assets/generated/res.bin` no longer reaches the signed apk (verified:
`jar tf` now lists `assets/mcpp-run.json` only, where it previously
also listed `assets/generated/res.bin`). This is a gap in
`run_shared_program`, not something this member can read around from
its own vantage point -- see this member's report for the two staged
trees compared side by side. `zipalign -f` and the `d8` `.class` glob
are unchanged (both remain measured facts, independent of this
change).
0 commit comments