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

Support both libsoup-2.4 and 3.0 #666

Merged
merged 1 commit into from
Jan 3, 2023
Merged

Support both libsoup-2.4 and 3.0 #666

merged 1 commit into from
Jan 3, 2023

Conversation

fnevgeny
Copy link
Member

No description provided.

@AndreasBilke
Copy link
Member

The current CI/CD does not catch this since ubuntu/windows use v2. To avoid possible compilation errors (maybe to changed symbols) it would be best to have that in the build process too.

But there is an ubuntu package for v3 (see https://packages.ubuntu.com/kinetic/libsoup-3.0-dev). Do you think a "build-libsoup-v3" step is a good option to handle this?

@fnevgeny
Copy link
Member Author

I believe the recommended approach is to use matrix builds, e.g., https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-using-a-single-dimension-matrix . But in any case, first this PR should be merged, otherwise all CI builds will fail. Kind of a chicken and egg problem :).

@fnevgeny fnevgeny linked an issue Dec 30, 2022 that may be closed by this pull request
@AndreasBilke AndreasBilke merged commit f628b0d into master Jan 3, 2023
@AndreasBilke AndreasBilke deleted the fix-664 branch January 3, 2023 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Support libsoup3
2 participants