Skip to content

Conversation

@anutosh491
Copy link
Member

No description provided.

Copy link
Member

@IsabelParedes IsabelParedes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea!

cd $HOME
git clone https://github.com/emscripten-core/emsdk.git
cd emsdk
./emsdk install ${{ matrix.emsdk_ver }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about we also add version 3.1.58 and/or latest to the matrix?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this was very beneficial for me atleast for xeus-cpp-lite. I think it would surely help with xeus-r !

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait actually no, I think there is a flaw here.

We fetch most things like r-base etc from emscripten-forge through environment-wasm-host.yml

We would want atleast the important packages in the toolchain like r-base, xeus-lite etc to be built against these versions too. (P.S: when I built xeus-cpp-lite against emsdk 3.1.73 ... first I had build errors cause llvm was build against 3.1.45 and once I addressed that, there were build errors from xeus-lite (some symbol mismatch or not exported) and then I built that against 3.1.73 and got xeus-cpp-lite working)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I think we should stick to 1 emsdk version for all pacakges for now (and I guess once emscripten-forge migrates to a new version like latest i.e. 3.1.73 on a separate branch) we can do this.

@anutosh491
Copy link
Member Author

anutosh491 commented Dec 13, 2024

That being said I think the wasm build env becomes redundant for the CI. Let me try removing it !
I'll mention in the readme PR that we need cmake so one can fetch it from micromamba

@IsabelParedes
Copy link
Member

This may not be necessary anymore, switched to using emsdk from emscripten-forge ( #116 ).

@anutosh491
Copy link
Member Author

anutosh491 commented Jan 15, 2025

switched to using emsdk from emscripten-forge

Yeah maybe the patched emsdk from emscripten-forge is a better option to use. (cc @martinRenou we might want to use the same for xeus, xeus-python etc ... I think all of them just clone from upstream)

@martinRenou
Copy link
Member

Agreed. I actually learned this week we had a patched emsdk on emscripten-forge :D

The patches only impact the runtime though, so if we're just testing compilation we may not reach any issue.

Still, it's better to use the patched one since this is the one being used on emscripten-forge and that's what we want to test.

@anutosh491 anutosh491 closed this Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants