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

Changed minimal version of C++ standard to C++17 #879

Closed
wants to merge 1 commit into from
Closed

Changed minimal version of C++ standard to C++17 #879

wants to merge 1 commit into from

Conversation

xvitaly
Copy link
Contributor

@xvitaly xvitaly commented Jan 31, 2023

Changed minimal version of C++ standard to C++14. Google Test since version 1.13.0 requires C++14.

Closes #877.

@veloman-yunkan
Copy link
Collaborator

The CI of this PR fails in the same way as #878 (thus the issue was not caused by the + symbol in the branch name). By looking closer it turns out that the checkout step attempts to clone the repository from kiwix rather than from @xvitaly's fork and fails because the branch is only present in the fork. This problem should be present with any PR created against a fork.

Now, looking in .github/workflows/ci.yml I see that the Checkout code step uses actions/checkout@v2 under macos (which works) but a custom command line under linux. I wonder why actions/checkout isn't used in the latter case.

The same issue with CI workflow configuration is present in libzim.

@veloman-yunkan
Copy link
Collaborator

@mgautierfr @kelson42 Do you know of any reason why actions/checkout is not used under linux in our CI?

@mgautierfr
Copy link
Member

Do you know of any reason why actions/checkout is not used under linux in our CI

There is a small information in the commit message here : openzim/libzim@34aba05f

The thing is that we reuse the dependencies build by kiwix-build and there is some (?) conflict between path and write rights.
I don't remember which one exactly. But if you want to fix that, you are more than welcome 😃

@kelson42
Copy link
Collaborator

kelson42 commented Feb 5, 2023

Actually we will should move straight to C++17.

@xvitaly
Copy link
Contributor Author

xvitaly commented Feb 5, 2023

Actually we will should move straight to C++17.

Should I update my PR to c++17?

@kelson42
Copy link
Collaborator

kelson42 commented Feb 5, 2023

@xvitaly As far as I understand from @mgautierfr, we have a few things to sort out before. For the moment I would just wait a bit. We might fix all of that this WE.

@xvitaly xvitaly changed the title Changed minimal version of C++ standard to C++14 Changed minimal version of C++ standard to C++17 Feb 7, 2023
@xvitaly
Copy link
Contributor Author

xvitaly commented Feb 7, 2023

Updated PR to C++17.

Google Test since version 1.13.0 requires C++14.

Signed-off-by: Vitaly Zaitsev <vitaly@easycoding.org>
@kelson42
Copy link
Collaborator

kelson42 commented Apr 1, 2023

Closing for the moment as we have external blockers. Might be reopened when they will be fixed.

@kelson42 kelson42 closed this Apr 1, 2023
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.

gtest C++14 requirement (move to C++17)
4 participants