-
Notifications
You must be signed in to change notification settings - Fork 350
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
Prefer using system Abseil if available #347
Conversation
I've also noticed some similar logic gated behind |
This enables use of our Abseil in bloaty. This is a backport of the patch upstreamed at google/bloaty#347.
Ping @haberman? |
Sorry for the long delay on this. The CI tests aren't running on this PR and I'm not sure why. They seems to be running on some PRs but not others. The tests ran on the most recently merged PR #370. I wonder if there is any chance that PR broke the CI. Any idea @arunsathiya? |
I am not sure just yet, but the workflows on the PR #370 were manually triggered by you, as a maintainer of the project.
Would something similar be required here? I am unable to see those workflows on the checks section of the current PR #347, possibly because I am not a maintainer of this project: |
I saw the button on the other PR and clicked it. But I don't see the button here. I am not sure why it disappeared. |
I rebased on |
The external Abseil build seems to choke at trying to build googletest. I've fixed that by pointing it at |
Newer versions of Protobuf (22+) pull in Abseil as a dependency. We want to avoid using our bundled copy for these cases, as this will likely conflict with the version of Abseil that Protobuf uses. The simplest way to do this seems to be to just prefer a system installation of Abseil if it's available. Signed-off-by: Carlo Cabrera <[email protected]>
Oops, that didn't work for some reason. I've just disabled Abseil's tests. |
Unfortunately I think I need to roll this back for now, as it broke the continuous build: https://github.com/google/bloaty/actions/runs/10566910014/job/29274712202#step:10:315
We may need to update the version of ABSL first. |
Alternatively, would you be interested in trying to fix the continuous build with a fix-forward? |
Sure, let me look at trying to update the bundled copy of abseil. |
Newer versions of Protobuf (22+) pull in Abseil as a dependency. We
want to avoid using our bundled copy for these cases, as this will
likely conflict with the version of Abseil that Protobuf uses.
The simplest way to do this seems to be to just prefer a system
installation of Abseil if it's available.
I've also cherry-picked from #207 to simplify what I want to do here.