-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[new port] gtk 3.24.34 port #22201
[new port] gtk 3.24.34 port #22201
Conversation
Could we see a gtkmm3 port as well? |
Sure, I will work on gtk3mm port |
Cool, thanks :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!
PRs must add only one version and must not modify any published versions
When making any changes to a library, the version or port-version in vcpkg.json
or CONTROL
must be modified.
Error: Local changes detected for gtk3 but no changes to version or port version.
-- Version: 3.24.30
-- Old SHA: 8fcadeff3c2eba6e6cd20b1158014c8f308dea54
-- New SHA: 4fb3acb0474e205624b3a2b4c1f02a45468be19c
-- Did you remember to update the version or port version?
-- Pass `--overwrite-version` to bypass this check.
***No files were updated.***
@mkhon ,Thanks for your pr, for the x86-windows error, you can run command "./vcpkg x-add-version gtk3 --overwrite-version " and commit again after you finish your pr.
and This is the detail error log please take a look: |
@mkhon , it looks the post build step failed. |
@mkhon ,It seems that the error has not been solved yet, here is the detailed error log |
@mkhon ,I encountered this error when verifying the feature, it seems that port pango does not have an introspection feature
|
@JonLiu1993 introspection feature is added in #22200 |
Depends on pr #22200 |
I fix the gkt ld error I got. It was bug in our end (boinc opensource project). |
set(warning_length 24) | ||
string(LENGTH "${CURRENT_BUILDTREES_DIR}" buildtrees_path_length) | ||
if(buildtrees_path_length GREATER warning_length AND CMAKE_HOST_WIN32) | ||
message(WARNING "${PORT}'s buildsystem uses very long paths and may fail on your system.\n" | ||
"We recommend moving vcpkg to a short path such as 'C:\\vcpkg' or using the subst command." | ||
) | ||
endif() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
set(warning_length 24) | |
string(LENGTH "${CURRENT_BUILDTREES_DIR}" buildtrees_path_length) | |
if(buildtrees_path_length GREATER warning_length AND CMAKE_HOST_WIN32) | |
message(WARNING "${PORT}'s buildsystem uses very long paths and may fail on your system.\n" | |
"We recommend moving vcpkg to a short path such as 'C:\\vcpkg' or using the subst command." | |
) | |
endif() | |
vcpkg_buildpath_length_warning(24) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vcpkg_buildpath_length_warning() can not be used here as it recommends to move to C:\src\vcpkg which gives buildpath length >24
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So can you confirm a longest valid path to replace this code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried subst
and it seems not solving the problem. Moving to the root of a drive may be the only choice.
I would also suggest we make it clear that the path length cannot exceed 24 (if that’s the exact number). This message could fail to inform the user of what kind of paths are acceptable.
I would like to hear from the maintainers, as we had this patch before and PR got rejected because of this. |
I'd like to wait for #24934 to add port at-spi2-atk first. |
I would like that too! But vcpkg don't install dubs on the ci for that. 😢 |
- Use vcpkg_from_gitlab()
set(warning_length 24) | ||
string(LENGTH "${CURRENT_BUILDTREES_DIR}" buildtrees_path_length) | ||
if(buildtrees_path_length GREATER warning_length AND CMAKE_HOST_WIN32) | ||
message(WARNING "${PORT}'s buildsystem uses very long paths and may fail on your system.\n" | ||
"We recommend moving vcpkg to a short path such as 'C:\\vcpkg' or using the subst command." | ||
) | ||
endif() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried subst
and it seems not solving the problem. Moving to the root of a drive may be the only choice.
I would also suggest we make it clear that the path length cannot exceed 24 (if that’s the exact number). This message could fail to inform the user of what kind of paths are acceptable.
Ping @mkhon for response. |
Convert this PR to draft since there is no progress. Please ping us if this PR is ready for review again. |
Waiting for #26766 merge first. |
Better that he will open this PR on his mkhon user. |
I opened a new PR #24136 for this |
#24136 this is my PR. I can open it. |
I think you meant this PR #27026 |
New port: gtk 3.24.34 (some software still requires GTK3)
What does your PR fix?
Which triplets are supported/not supported? Have you updated the CI baseline?
all
Does your PR follow the maintainer guide?
Yes
If you have added/updated a port: Have you run
./vcpkg x-add-version --all
and committed the result?Yes
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/