Hi Jonas,

I've had a quick look at emcc now. I don't feel comfortable adding a ccache
symlink for it without some kind of evaluation of how emcc's options interact
when using the "-c" mode -- a symlink in /usr/lib/ccache would signal that
ccache officially supports emcc, which it doesn't (yet).

>From "emcc --help" I see that the following options take an argument, which is
something that ccache would need to be taught about to work properly:

    --closure
    --js-transform
    --llvm-opts
    --memory-init-file
    --minify
    --output_eol
    --source-map-base
    --valid-abspath
    -s

On the other hand, perhaps none of these are applicable (or used in practice)
when using "-c", but that's not something I can rule out.

This option definitely isn't compatible with ccache since it changes the output
filename:

    --default-obj-ext

These options take an argument that refers to an input file which ccache should
read and hash separately as part of the input:

    --embed-file
    --exclude-file
    --extern-post-js
    --extern-pre-js
    --js-library
    --post-js
    --pre-js
    --preload-file
    --shell-file

Again, maybe none of those are applicable when using "-c" but I can't really
tell.

These produce another output file which would need to be cached by ccache:

    -gseparate-dwarf
    --emit-symbol-map

They don't seem to have any effect when using "-c", though?

Some environment variables (EMMAKEN_CFLAGS, EMCC_CLOSURE_ARGS) maybe also need
special treatment?

Regards,
Joel

On Thu, 15 Oct 2020 at 12:39, Jonas Smedegaard <d...@jones.dk> wrote:
>
> Package: ccache
> Version: 3.7.12-1
> Severity: normal
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> The emcc command part of emscripten supports ccache:
> https://github.com/emscripten-core/emscripten/issues/11974
>
> Please ship the Debian ccache package with symlink for emcc.
>
>  - Jonas
>
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+IJmQACgkQLHwxRsGg
> ASHfYQ/8DGUQ8OMRwT2w/SSnFpkTghr0TkNbEb45YwAY8xuSL0oAQR5+roQ313Nj
> oBGBovDd1lDa/D3uOuCfcLkNxH3C4s0hvZ/fh38XU1QN9F2HZWfkzpvaL5FGbt7+
> GbRtwxPRAu8NwJkwvecQKKRNEAyS/pLdQ1U04ephVjDsNh4dTn7nS2pEOUfO/Dwo
> 6UiU+FMupQDq0EaSPpakczFSZRRdtaBuBYkBuHVkMUild3GVrQZr5pOFogF+S823
> hsnvMmkmaZ1PEpOueU0iD8Yvj8k2EO5nT5iN3+b9vm/o2HezKDNC1YchhjmBjjxL
> oQF1TOeAl+E5WZDKx/9TVgpnXqSLWbANyoICzMCpumfLSYNm/88TraFd8AE7eLSc
> O1BZkXId4Rb3ZwCbucMz+rWo8lHvFMaUuCTuQuXLwCE7ieFhhcNuvg62NEw9c7lt
> E896UwlcGVcEvaao1vvLobeaTO+NY+a0CqdQO8Oipe8VSMP9MG+iKezNferJwbXa
> K8lof9cYe9inTgchdQXUOPPEEkT3Y/Eii1Mh4sDxaMphFct9y+CNwRHz5xjZLW5N
> nZSZlr+Z0SRe2s0J6XfyfBkXzx/VicDwLnji8i5/ENZCiShraabl6v6wGtPltOMJ
> +9AcRB7MneolTxFSaGN37T+ARpYNgPEu3NolS0d2BJEJai4wxf4=
> =DEVw
> -----END PGP SIGNATURE-----
>

Reply via email to