Skip to content

MEMORY64=2 clarification #26263

Closed
Closed

Description

@arsnyder16

Curious if this use case is supported.

I have a number of third party external libraries that i build into static libraries. Can i build those libraries with MEMORY64=2 and then later link them into my module for both MEMORY64=1 and MEMORY64=2. Basically i am wondering if i can avoid creating two sets of static libraries and let binaryen lower everything after when i produce wasm32

Activity

  1. sbc100 commented on Feb 13, 2026

    @sbc100
    Collaborator

    Yes -sMEMORY64=2 it really just a link time setting.

  2. arsnyder16 commented on Feb 13, 2026

    @arsnyder16
    ContributorAuthor

    Thank you, that was my hope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions