Skip to content

[wasm] move emsdk setup from runtime to emsdk tooling #105439

Closed
Closed
[wasm] move emsdk setup from runtime to emsdk tooling#105439
Assignees
ilonatommy
Labels
arch-wasmWebAssembly architecturearea-Build-monoin-prThere is an active PR which will close this issue when it is merged
Milestone
Future

Description

@lewing
lewing
opened on Jul 24, 2024

Right now src/mono/mono.proj has complicated logic to use the emsdk packages to build runtime, that setup logic should be moved to emsdk and used where do similar things (like dotnet/icu)

see #105437 for an example

  • emscripten config file
  • Linux/Windows scripts emsdk_env*

Activity

  1. ghost added
    area-Build-mono
    on Jul 24, 2024
  2. lewing
    added this to the 9.0.0 milestone on Jul 24, 2024
  3. ilonatommy
    self-assigned this
    on Jul 29, 2024
  4. lewing
    modified the milestones: 9.0.0, 10.0.0 on Aug 14, 2024

  5. lewing commented on Aug 14, 2024

    @lewing
    lewing
    on Aug 14, 2024
    MemberAuthor

    tis is infrastructure and not blocking so I'm moving to 10

  6. dotnet-policy-service
    added
    in-prThere is an active PR which will close this issue when it is merged
    on Aug 14, 2024
  7. lewing
    modified the milestones: 10.0.0, Future on Jun 21, 2025
  8. pavelsavara
    added
    arch-wasmWebAssembly architecture
    on Jul 10, 2026

  9. dotnet-policy-service commented on Jul 10, 2026

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Jul 10, 2026 – with Dotnet Policy Service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
    See info in area-owners.md if you want to be subscribed.

  10. lewing
    closed this as completedon Sep 13, 2026
  11. github-actions
    locked and limited conversation to collaborators on Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

arch-wasmWebAssembly architecturearea-Build-monoin-prThere is an active PR which will close this issue when it is merged

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions