Skip to content

Conversation

@st0012
Copy link
Member

@st0012 st0012 commented Jan 10, 2025

Instead of uploading the built libprism.so and libprism.dylib, which still requires headers files to be built, Prism can upload the full source, headers, and the Makefile as a tarball that can be used to build libprism from source.

The reason default release artifacts are not enough is because some source and header files are generated through Prism's rake tasks.

Example release: https://github.com/Shopify/prism/releases/tag/v1.3.2

Note: This is @paracycle's brilliant idea 🚀

Instead of uploading the built `libprism.so` and `libprism.dylib`,
which still requires headers files to be built, Prism can upload the
full source, headers, and the Makefile as a tarball that can be used to
build libprism from source.

The reason default release artifacts are not enough is because some
source and header files are generated through Prism's rake tasks.
@st0012 st0012 force-pushed the add-libprism-artifacts branch from 52eb0e0 to b8258ca Compare January 10, 2025 20:33
Copy link
Collaborator

@paracycle paracycle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thank you!

matrix:
os: [ubuntu-latest, macos-latest]
runs-on: ${{ matrix.os }}
runs-on: ubuntu-latest
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we're not building binary files anymore, we don't need to run this on multiple systems.

@paracycle paracycle merged commit 080304e into ruby:main Jan 10, 2025
56 of 58 checks passed
@paracycle paracycle deleted the add-libprism-artifacts branch January 10, 2025 20:58
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.

2 participants