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.

Sign up for GitHub

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

Jump to bottom

Use bundle install --target-rbconfig to install gems for Wasm target #490

Open
wants to merge 11 commits into
base: main
Choose a base branch
from
Open

Use bundle install --target-rbconfig to install gems for Wasm target #490

wants to merge 11 commits into from
+216 −58

Commits on Jul 17, 2024

  1. Use bundle install --target-rbconfig to install gems for Wasm target

    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    89fc464 View commit details
    Browse the repository at this point in the history

  2. Fix Gemfile.lock issue

    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    5a5ed12 View commit details
    Browse the repository at this point in the history

  3. Try to fix Gemfile.lock auto-self-downgrade issue

    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    483ae14 View commit details
    Browse the repository at this point in the history

  4. Upload artifact before running tests 

    This helps investigate test failures
    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    3f905d5 View commit details
    Browse the repository at this point in the history

  5. Make --enable-component-model the default for js gem 

    In this way, we can avoid the need to specify `BUNDLE_BUILD__JS=--enable-component-model`
when running `bundle install` for the `js` gem. When running `bundle install`, it's usually
dynamic-linking enabled, so it makes sense to enable the component model by default.
    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    232b8dc View commit details
    Browse the repository at this point in the history

  6. Use vendor/cache for js gem to build extension as a part of "bundle i… 

    …nstall"
    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    76bd2c4 View commit details
    Browse the repository at this point in the history

  7. Update release instructions to include bump_dev_version task

    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    3fca025 View commit details
    Browse the repository at this point in the history

  8. Fix bin/setup not to install ruby-head-wasm-wasi's Gemfile 

    The ruby-head-wasm-wasi's Gemfile uses vendor/cache to install js gem
but the cache gem is not yet available at setup-time. And also with
cache gem, the Gemfile is not needed to be installed at setup-time.
So just skip the Gemfile installation here
    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    6703565 View commit details
    Browse the repository at this point in the history

  9. Create vendor gem cache before computing cache key for npm package

    @kateinoigakukun
    kateinoigakukun committed Jul 17, 2024
    Configuration menu
    Copy the full SHA
    d787c23 View commit details
    Browse the repository at this point in the history

Commits on Jul 19, 2024

  1. Update Gemfile.lock

    @kateinoigakukun
    kateinoigakukun committed Jul 19, 2024
    Configuration menu
    Copy the full SHA
    54742bc View commit details
    Browse the repository at this point in the history

  2. Seems like bundler respects the .gem file name

    @kateinoigakukun
    kateinoigakukun committed Jul 19, 2024
    Configuration menu
    Copy the full SHA
    0b66668 View commit details
    Browse the repository at this point in the history