Skip to content

Revert "CI: Workaround OSGeo4W OpenSSL DLL conflict by forcing one" #7960

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

Merged
echoix merged 1 commit into from
Sep 27, 2026
Merged

Revert "CI: Workaround OSGeo4W OpenSSL DLL conflict by forcing one" #7960

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 0 additions & 14 deletions .github/workflows/osgeo4w.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,20 +98,6 @@ jobs:
sqlite3-devel
zstd-devel

# Python in OSGeo4W bundles OpenSSL 3.0 DLLs with the same names as the
# OSGeo4W OpenSSL 3.5 DLLs. Once a process imports ssl, libcurl loaded
# later (by GDAL or PROJ) binds to the older libssl, but curl 8.22 needs
# SSL_get0_group_name from OpenSSL 3.2, so loading GDAL or GRASS
# libraries fails. OpenSSL 3 keeps its ABI across minor versions, so
# Python can use the newer DLLs.
- name: Use OSGeo4W OpenSSL DLLs in Python
run: |
Copy-Item -Path "$env:O4WROOT\bin\libssl-3-x64.dll", "$env:O4WROOT\bin\libcrypto-3-x64.dll" `
-Destination "$env:O4WROOT\apps\Python312\DLLs" -Force
shell: pwsh
env:
O4WROOT: ${{ steps.osgeo4w.outputs.root }}

- name: Set number of cores for compilation
run: |
echo "MAKEFLAGS=-j$(nproc)" >> "${GITHUB_ENV}"
Expand Down
Loading