Skip to content

Emit library names as a manifest from the linking step #497

Open

Description

@kraenhansen

Make the library name data rather than a shared algorithm: the linking step emits a manifest that JS reads. JS and the linker then can't disagree about a name, and per-library overrides (#368) have somewhere to live. getLibraryMap() already computes this map.

This is a change to our own tooling. Related: #222, #91.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Linking 🔗Discovering and copying prebuilds from packages into the hostenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions