-
Notifications
You must be signed in to change notification settings - Fork 715
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
I tried installing emsdk in WSL, but didn't clang++ or llvm-link #172
Comments
I was able to get it to work. It's just that now I can't get the I'll make another issue about the thing after the "Edit" in the original post. |
vargaz
pushed a commit
to vargaz/emsdk
that referenced
this issue
Nov 22, 2023
* Workload changes and arcade update (emscripten-core#171) (emscripten-core#172) * Update arcade to 7.0.0-beta.22416.1 * Workload changes Co-authored-by: Larry Ewing <lewing@microsoft.com> Co-authored-by: Juan Hoyos <juan.hoyos@microsoft.com> * [release/7.0-rc1] Make two manifests one for net7 and one for net6 in 7.0.100 sdk band (emscripten-core#163) * Here goes nothing * Update WorkloadManifest.json.in * Update WorkloadManifest.json.in * Try to fix up the multi-targeted build. This will likely need an arcade change to enable manifests withtout packs and an additional change once arcade is updated. * Update eng/emsdk.proj Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> * Rename .pkgproj files * Update PackageVersionNet6 to 6.0.9 * Fix the location of the .net7 pkgproj Co-authored-by: Marc Paine <marcpop@microsoft.com> Co-authored-by: Ankit Jain <radical@gmail.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> * [release/7.0-rc1] Shorten the name more (emscripten-core#174) * Shorten the name more * [release/7.0-rc1] Check nuget sizes and fix them (emscripten-core#175) * yml: Fail if nuget size exceeds 250MiB, on linux, and macos * Fix the case for no errors * Remove unused binaries Co-authored-by: Ankit Jain <radical@gmail.com> * Add PowerShell-based NuGet size check script and use it on Windows (emscripten-core#176) * Add PowerShell-based NuGet size check script and use it on Windows * Update azure-pipelines.yml Co-authored-by: Juan Hoyos <juan.hoyos@microsoft.com> Co-authored-by: Marc Paine <marcpop@microsoft.com> Co-authored-by: Ankit Jain <radical@gmail.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
vargaz
pushed a commit
to vargaz/emsdk
that referenced
this issue
Nov 22, 2023
* Workload changes and arcade update (emscripten-core#171) (emscripten-core#172) * Update arcade to 7.0.0-beta.22416.1 * Workload changes Co-authored-by: Larry Ewing <lewing@microsoft.com> Co-authored-by: Juan Hoyos <juan.hoyos@microsoft.com> * [release/7.0-rc1] Make two manifests one for net7 and one for net6 in 7.0.100 sdk band (emscripten-core#163) * Here goes nothing * Update WorkloadManifest.json.in * Update WorkloadManifest.json.in * Try to fix up the multi-targeted build. This will likely need an arcade change to enable manifests withtout packs and an additional change once arcade is updated. * Update eng/emsdk.proj Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> * Rename .pkgproj files * Update PackageVersionNet6 to 6.0.9 * Fix the location of the .net7 pkgproj Co-authored-by: Marc Paine <marcpop@microsoft.com> Co-authored-by: Ankit Jain <radical@gmail.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> * [release/7.0-rc1] Shorten the name more (emscripten-core#174) * Shorten the name more * [release/7.0-rc1] Check nuget sizes and fix them (emscripten-core#175) * yml: Fail if nuget size exceeds 250MiB, on linux, and macos * Fix the case for no errors * Remove unused binaries Co-authored-by: Ankit Jain <radical@gmail.com> * Add PowerShell-based NuGet size check script and use it on Windows (emscripten-core#176) * Add PowerShell-based NuGet size check script and use it on Windows * Update azure-pipelines.yml * Roll back 6.0.x to 6.0.8 so that packages exist (emscripten-core#177) * Revert "Roll back 6.0.x to 6.0.8 so that packages exist (emscripten-core#177)" (emscripten-core#178) This reverts commit b7a5ae2. * make a 6.0.4 build (emscripten-core#180) * Revert "make a 6.0.4 build (emscripten-core#180)" (emscripten-core#181) This reverts commit eb3232e. * [release/7.0] Update arcade to 7.0.0-beta.22418.4 (emscripten-core#182) * WorkloadManifest.targets: fix condition (emscripten-core#183) Co-authored-by: Juan Hoyos <juan.hoyos@microsoft.com> Co-authored-by: Marc Paine <marcpop@microsoft.com> Co-authored-by: Ankit Jain <radical@gmail.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried installing emsdk in WSL (Windows 10), but I didn't get clang++ or llvm-link. I'm having a hard time building the Hello World application in the Developer's Guide because of this issue. I want to reinstall emsdk by cloning the repository directly into Windows instead of using the bash command line in WSL. Is there a way to make sure I can get all of the necessary files? Please help me out.
Thanks in advance.
Edit: I'd also like to know if it's possible to write an application that's both a WebAssembly application and also uses Boost.Beast. I wrote a web app with the frontend code in HTML, CSS and JavaScript with the backend being a web server written using Boost.Beast as well as Jinja2Cpp and NlohmannJson. It also has two environment variables. I'm having a hard time figuring out how to deploy it. I have a subdomain I got from freedns.afraid.org as well.
The text was updated successfully, but these errors were encountered: