Attempt to load compiled library from lib and ext to handle rubygems …

[thekendalmiller]

…moving the library

This seems to be how other gems with native extensions handle it

[Laykou]

I see this is fixes issue when upgrading to Ruby 3.2.

Could this be merged?

[alishersadikov]

We are upgrading our Ruby version and ran into the underlying issue too. Hoping it can be merged soon.

[caiobsilva]

Thank you for this! Are the maintainers aware/planning to merge this issue?
@dbalatero? 👀

[Laykou]

Could this be merged please?

[harto]

+1, would be great to have this fix incorporated

[Laykou]

Could this be merged and released as a new version please?

[BigAirJosh]

another bump for a merge 🙏

[Estiennejeremy]

Another up too for the merge please 🙏

[dbalatero]

Sorry, I haven't been working in Ruby for quite a few years now and need to page all this back into memory.

I can merge but I don't want to break old Ruby versions. This repo lacks CI, so I think I'd like to add that first, then see if this PR passes CI (maybe on a matrix of versions). Let me do that first, then look at this PR.

For now, you can point your Gemfiles at the fork/branch that implements this, if you need the fix today.

[dbalatero]

Blegh, I tried to open a PR against my own repo but it's going to the repo I forked from years ago. I think I either have to push my broken CI PR to master to add CI support, or detach from the fork to get my CI PR in.

I can detach this repo from the original repo, but it will drop all pull requests and issues and recreate the repo, so we'll lose all the bug context here which also sucks.