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

FOR TESTING ONLY: test windows clang-cl workflow #2288

Closed

Conversation

wantehchang
Copy link
Collaborator

clang-cl compilation should fail.

@wantehchang wantehchang marked this pull request as draft July 18, 2024 00:55
@vrabaud
Copy link
Collaborator

vrabaud commented Jul 18, 2024

It passes so I guess we need more warning flags?

@wantehchang
Copy link
Collaborator Author

I am also puzzled why it passed. I think it is because Chrome enables C++ version >= 17. We enable C++14.

I just checked Google's Foundational C++ Support table. It supports C++ >= 14. So we should not enable C++17 yet. Our only option is to set -DAVIF_ENABLE_NODISCARD=ON in the clang-cl CI workflow. Not sure if we should do that. I will do that as an experiment in this test pull request.

For now, let's just import into Chrome frequently.

@wantehchang wantehchang force-pushed the test-clang-cl-ci-workflow branch 24 times, most recently from 0dd4335 to 2918f21 Compare July 22, 2024 21:34
@wantehchang wantehchang force-pushed the test-clang-cl-ci-workflow branch from 794720c to 17edf54 Compare July 30, 2024 00:24
@wantehchang
Copy link
Collaborator Author

This pull request was just a test. Test completed.

@wantehchang wantehchang deleted the test-clang-cl-ci-workflow branch July 31, 2024 21:04
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.

2 participants