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.
Clones emsdk and uses it rather than fetching emsdk from conda-forge (just like xeus-python, xeus-cpp etc)
I think
CMAKE_FIND_ROOT_PATH_MODE_PACKAGE
is being used wrongly.Cmake docs say that there are only 3 values this variables accepts
i) ONLY
ii) NEVER
iii) BOTH
What we are using is something like
CMAKE_FIND_ROOT_PATH_MODE_PACKAGE=ON
which doesn't make sense.As the docs say
CMAKE_FIND_ROOT_PATH_MODE_PACKAGE
basically controls two variablesi)
CMAKE_FIND_ROOT_PATH
ii)
CMAKE_SYSROOT
As far as my understanding goes we just need to control the
CMAKE_FIND_ROOT_PATH
that cmake uses while cross-compiling.When cross-compiling (for example, when using Emscripten), CMake normally uses the host system's root directory as the search root.
CMAKE_FIND_ROOT_PATH
allows you to override this behaviour and specify alternate directories that CMake should treat as the root for package discovery.So in this case we don't even need to control both vars through
CMAKE_FIND_ROOT_PATH_MODE_PACKAGE
asCMAKE_SYSROOT
is not really of use to us.