Skip to content

[vcpkg] Fix name clash (e.g. "all" build for triplet x64-windows-release and "release" build for triplet x64-windows)#22501

Closed
mkhon wants to merge 1 commit intomicrosoft:masterfrom
soylent-io:fix/z_vcpkg_get_cmake_vars-name-clash
Closed

[vcpkg] Fix name clash (e.g. "all" build for triplet x64-windows-release and "release" build for triplet x64-windows)#22501
mkhon wants to merge 1 commit intomicrosoft:masterfrom
soylent-io:fix/z_vcpkg_get_cmake_vars-name-clash

Conversation

@mkhon
Copy link
Copy Markdown
Contributor

@mkhon mkhon commented Jan 12, 2022

Describe the pull request

This fixes name clash still left after 7534d24

  • What does your PR fix?

  • Which triplets are supported/not supported? Have you updated the CI baseline?

all

Yes

  • If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

N/A

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

and "release" build for triplet x64-windows).
@mkhon
Copy link
Copy Markdown
Contributor Author

mkhon commented Jan 12, 2022

@strega-nil-ms

@LilyWangLL LilyWangLL added the category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed label Jan 12, 2022
@LilyWangLL LilyWangLL self-assigned this Jan 12, 2022
@LilyWangLL LilyWangLL changed the title Fix name clash (e.g. "all" build for triplet x64-windows-release and "release" build for triplet x64-windows) [vcpkg] Fix name clash (e.g. "all" build for triplet x64-windows-release and "release" build for triplet x64-windows) Jan 14, 2022
@LilyWangLL LilyWangLL added the info:needs-maintainer-attention Lets the current 'on rotation' vcpkg maintainer know they need to look at this. label Jan 14, 2022

if(DEFINED VCPKG_BUILD_TYPE)
set(cmake_vars_file "${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}-${VCPKG_BUILD_TYPE}.cmake.log")
set(cmake_vars_file "${CURRENT_BUILDTREES_DIR}/cmake-vars-${TARGET_TRIPLET}.${VCPKG_BUILD_TYPE}.cmake.log")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't quite understand; doesn't this need to match the paths on 54 and 55? That one uses dashes rather than dots.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No, it should not have to match these because this file includes one (or both) of defined at lines 54 and 55

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe then we should add a name like "combined" rather than expecting a . rather than - to convey all the meaning here?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ping @mkhon for response.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It was "cmake-vars-${TARGET_TRIPLET}.cmake.log" before 7534d24
I only wanted to change it to "cmake-vars-${TARGET_TRIPLET}.${VCPKG_BUILD_TYPE}.cmake.log"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

What I mean is, having two files with semantically different contents looks like a bug, and I can easily see the next person recreating the bug you're trying to fix here by renaming it back. I don't care what was before, I only care about making this code understandable and making it unlikely that we will recreate the problem again.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ping @mkhon for response

@BillyONeal BillyONeal added requires:author-response and removed info:needs-maintainer-attention Lets the current 'on rotation' vcpkg maintainer know they need to look at this. labels Jan 14, 2022
@mkhon
Copy link
Copy Markdown
Contributor Author

mkhon commented Jan 25, 2022

Can we push this minor fix?

@mkhon
Copy link
Copy Markdown
Contributor Author

mkhon commented Jan 25, 2022

requires:author-response tag should also be removed from here

@BillyONeal
Copy link
Copy Markdown
Member

requires:author-response tag should also be removed from here

I don't believe #22501 (comment) has a response

@LilyWangLL
Copy link
Copy Markdown
Contributor

@mkhon Can you reply the review suggestions? Thanks!

@LilyWangLL
Copy link
Copy Markdown
Contributor

Closing this PR since it seems that no progress is being made. Please reopen if work is still being done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants