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

Rework Windows resources hack to not depend on resource path strings #104

Merged
merged 2 commits into from
Jan 22, 2024

Conversation

ugexe
Copy link
Collaborator

@ugexe ugexe commented Jan 21, 2024

Rakudo recently started emitting deprecation messages when %?RESOURCES was treated like a path string (see rakudo/rakudo#5507). That affects these openssl bindings because a windows-specific hack was using the base file name of a %?RESOURCE entry, which would cause the aforementioned deprecation messages to be emitted. This PR reworks the hack to not depend on any part of the path name.

ugexe added 2 commits January 20, 2024 22:30
When doing CI tests it is important to also test that the install
itself works. However, due to how precompilation works with staging
repositories the fastest way to both run the tests and test the
actual install is to run `zef install .`. Doing so avoids an extra
round of precompilation over doing a test step followed by an
install step.
Previously we were copying dll files from resources to a different
location so that the files could continue having the same file
name. There was also a hack to avoid doing that copy and to use
the included dll files directly if it determined those resources
already had the expected basename (such as a non-installed openssl).
The hack relied on using now deprecated methods, but realistically
we don't need it.

This reworks the logic on Windows for copying a resource file to
always occur regardless of what repository has loaded it. By doing
so it fixes some deprecation messages from rakudo about treating
resource objects like path strings.

See: rakudo/rakudo#5507
@ugexe ugexe merged commit 2ca6421 into sergot:main Jan 22, 2024
3 checks passed
@ugexe ugexe deleted the fix-deprecations branch January 22, 2024 02:33
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.

1 participant