Skip to content

Add FFI::addLibraryPath utility #264

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

Merged
merged 2 commits into from
Apr 4, 2025
Merged

Conversation

kleisauke
Copy link
Member

@kleisauke kleisauke commented Feb 21, 2025

Resolves: #232.
Supersedes: #245.

In favor of the `VIPSHOME` env.

Resolves: libvips#232.
@kleisauke kleisauke marked this pull request as ready for review April 4, 2025 11:30
@jcupitt jcupitt merged commit 1ffcd1f into libvips:master Apr 4, 2025
6 checks passed
@jcupitt
Copy link
Member

jcupitt commented Apr 4, 2025

Sweet!

Do you think we're OK for a new php-vips release now? Any thoughts @pizcadesaber ?

@pizcadesaber
Copy link

@jcupitt I've taken a look at the different pull requests, and I think they address the two issues I highlighted in Termux. Thanks everyone for your work!

@jcupitt
Copy link
Member

jcupitt commented Apr 4, 2025

OK, I've tagged v2.4.2 with all these changes. Any testing is very welcome!

@kleisauke kleisauke deleted the issue-232 branch April 4, 2025 16:29
@jcupitt
Copy link
Member

jcupitt commented Apr 4, 2025

Wait, I'm being very dumb, there has been an API addition, so we should have a minor version bump, sorry about that.

I've deleted v2.4.2 and made v2.5.0.

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.

VIPSHOME misused/unsupported on Windows
3 participants