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

pluginify 0.6.0 #35

Merged
merged 1 commit into from
Aug 24, 2023
Merged

pluginify 0.6.0 #35

merged 1 commit into from
Aug 24, 2023

Conversation

itowlson
Copy link
Contributor

No description provided.

Signed-off-by: itowlson <[email protected]>
@ThorstenHans
Copy link
Contributor

yeah! 🎉 pluginify looks really helpful.

@itowlson Do you consider adding support for cross-compilation? This would allow plugin authors to cycle through everything in the inner-loop?

@itowlson
Copy link
Contributor Author

@ThorstenHans spin pluginify doesn't handle the actual building (though @cardoso has been mulling that). If you're cross-compiling, there is some minimal ability to override the OS and architecture generated into the manifest via the --os and --arch switches, but it doesn't currently handle cross-compilation into different directories (e.g. when your x86 build is in /target/release/foo and your ARM64 build is /target/linux-arm64/release/foo). This was sufficient for CI, where each target could be a separate runner, but there's definitely scope for making it more flexible (which might simplify the CI story too). If you want to raise an issue with more details of what would work well for you, that would be super useful - thanks! (https://github.com/itowlson/spin-pluginify/ to save you digging around in the JSON)

@itowlson itowlson merged commit c6da386 into fermyon:main Aug 24, 2023
2 checks passed
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

Successfully merging this pull request may close these issues.

3 participants