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

[CMake] Enable new policy for CMAKE_MSVC_DEBUG_INFORMATION_FORMAT #82371

Merged
merged 4 commits into from
Mar 12, 2024

Conversation

dabrahams
Copy link
Contributor

No description provided.

Copy link

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be
notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write
permissions for the repository. In which case you can instead tag reviewers by
name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review
by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate
is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot llvmbot added the cmake Build system in general and CMake in particular label Feb 20, 2024
@mstorsjo
Copy link
Member

Oh, and in addition to the comment wording suggestion, I think we also should change the subject of the PR (which also becomes the subject of the commit after merging), to indicate what actually changes - a cmake policy affecting how the project is built for everybody, in msvc mode. E.g. Subject: [CMake] Enable new policy for CMAKE_MSVC_DEBUG_INFORMATION_FORMAT. That will better catch the attention for anybody who might be affected by the change.

@dabrahams dabrahams changed the title Enable the use of SCCache for debug builds on Windows [CMake] Enable new policy for CMAKE_MSVC_DEBUG_INFORMATION_FORMAT Feb 22, 2024
@dabrahams
Copy link
Contributor Author

I think we also should change the subject of the PR

Done.

@@ -10,3 +10,17 @@ endif()
if(POLICY CMP0116)
cmake_policy(SET CMP0116 OLD)
endif()

+# Enable debug info compatible with SCCache
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this point, this first line feels a bit out of place (and kinda redundant with the stuff on lines 20-23 below), can we just remove this one?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ping - if you'd have time to update this to remove the first comment line here, I'd be ok with merging this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

cmake/Modules/CMakePolicy.cmake Outdated Show resolved Hide resolved
cmake/Modules/CMakePolicy.cmake Outdated Show resolved Hide resolved
Copy link
Member

@mstorsjo mstorsjo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

I'll go ahead and merge this tomorrow, unless someone else does it before me (or has something else to say on it).

@mstorsjo mstorsjo merged commit 23ffb2b into llvm:main Mar 12, 2024
3 of 4 checks passed
Copy link

@dabrahams Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested
by our build bots. If there is a problem with a build, you may recieve a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as
the builds can include changes from many authors. It is not uncommon for your
change to be included in a build that fails due to someone else's changes, or
infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself.
This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

# (https://github.com/mozilla/sccache?tab=readme-ov-file#usage)
# avoiding “fatal error C1041: cannot open program database; if
# multiple CL.EXE write to the same .PDB file, please use /FS"
+if(POLICY CMP0141)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, here, an extra + char had slipped in at the start of each line, breaking every single buildbot we have. But I pushed a fix in 1b945e3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmake Build system in general and CMake in particular
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants