emscripten-core / emscripten-core/setup-emsdk

Cache system libraries

Open
#6 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
123
Forks
34
PR merge metrics
No merged PRs in 30d

Description

First of all, thanks a lot for putting this out there; I've started using it today and it worked flawlessly in the first try.

This is not an issue but a feature request. It seems like the cache is being stored at the end of ` Run mymindstorm/setup-emsdk@v5`, so system libraries built during the "normal" compilation are not cached.

In my test build, generating these libraries take ~1m 40s (out of ~2m). Extract:
```
Tue, 07 Jul 2020 12:11:04 GMT
cache:INFO: generating system library: libc.a... (this will be cached in "/home/runner/work/bq-tiler/bq-tiler/emsdk-cache/emsdk-master/upstream/emscripten/cache/wasm-lto/libc.a" for subsequent builds)
Tue, 07 Jul 2020 12:12:08 GMT
cache:INFO: - ok
Tue, 07 Jul 2020 12:12:08 GMT
cache:INFO: generating system library: libcompiler_rt.a... (this will be cached in "/home/runner/work/bq-tiler/bq-tiler/emsdk-cache/emsdk-master/upstream/emscripten/cache/wasm-lto/libcompiler_rt.a" for subsequent builds)
```

Is there any way to setup a post run step to the build (either manually in each job or by adding an option to the action) to get those system libraries to also be cached? As far as I know, these generated system libraries only depend on the emcc version, so caching everything together should be safe.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.