Redirect $(WASM)/lib/R/bin
JS binaries to use native R
#367
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The binaries built by Emscripten in
$(WASM)/lib/R/bin
are JavaScript output, unable to be run directly by the host machine. Such binaries can be run using Node, but require some further setup (e.g. relocation of the requiredR.wasm
file).Since these scripts do not work when executed directly,
Makevars
targets relying on running R code using$(R_HOME)/bin/R
fail. Thesymbols.rds
target inlib/share/make/shlib.mk
is an example of this issue.With this commit, these specific scripts are redirected to use the version of R compiled for the host machine, working around the problem.
This should hopefully fix r-wasm/rwasm#13.