-
Notifications
You must be signed in to change notification settings - Fork 33
Recent releases use clang++ #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Ankit Jain <radical@gmail.com>
symlinks would be very nice. |
|
Adding some background. After upgrading emscripten windows AOT builds using these packages started failing because they were calling clang++ (not clang) and on windows clang++ was not included in the package. clang and clang++ are actually the same binary but since there is no way to express a symbolic link (or a literal duplicate) in a nupgk(zip) we have to make a copy. Unfortunately making a copy appears to push us over the nuget.org size limit on Windows because of enormous binaries. this appears to have pushed us over the nuget.org package size limit. |
|
I tried to strip the |
|
The I wonder if we can reduce it. Another possibility would be to split the nuget and have cache in a separate one. That would bring the size back under 250M. |
|
The original cache: the MINIMAL cache ( I think we might try to remove few libs to shrink the nuget size.
|
|
Plus all the |
Delete these libs on windows, where we are over the nuget size limit. Context: dotnet#34 (comment) That should affect build times when using [debug sanitizers](https://emscripten.org/docs/debugging/Sanitizers.html), which is not a common scenario I think.
|
Another option might be to try set https://github.com/emscripten-core/emscripten/blob/main/tools/shared.py#L823 |
|
Related emscripten change emscripten-core/emscripten@2470230 |
we need to test the workloads in use before upgrading too.
On windows,
emccends up invoking"C:\Program Files\dotnet\packs\Microsoft.NET.Runtime.Emscripten.2.0.23.Sdk.win-x64\6.0.0-preview.7.21323.1\tools\bin\clang++.exe", but that file is missing on the sdk package.And that manifests as: