Skip to content
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

Representation for native code #270

Open
npmccallum opened this issue Dec 16, 2021 · 4 comments
Open

Representation for native code #270

npmccallum opened this issue Dec 16, 2021 · 4 comments

Comments

@npmccallum
Copy link

I know that bindle was designed with WASM in mind. But I thought I'd just toss out something to think about. Bindle currently has no way to represent parcel's that are equivalent binaries for different CPU ISAs. For example, what if you build the same binary for x86_64 and aarch64? How should the client know which to download?

@radu-matei
Copy link
Member

The feature selection section in the label spec should provide a starting point for this.
I think that if we specify some standard label / feature keys, this could be solved such as when requesting the bindle and a desired value for the label (in this case the architecture), the client would get the proper artifact.

@npmccallum
Copy link
Author

@radu-matei Indeed. I had a similar thought. However, I'm worried that this will become overloaded with other concerns like build versioning (#266) and build variants (#269). All three of these concerns are vying for the same space.

@technosophos
Copy link
Contributor

See #269 (comment)

WasmCloud already uses Bindle this way.

@thomastaylor312
Copy link
Contributor

Yep, see here for a full example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants