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

[cleanup] Get rid of need for external/ on z3 library includes #1740

Closed

Conversation

cdleary
Copy link
Collaborator

@cdleary cdleary commented Nov 21, 2024

Towards #1736

For verible we can probably patch the cc_library targets we depend on to add the include_prefix attribute similarly.

@cdleary cdleary requested a review from meheff November 21, 2024 19:29
@cdleary cdleary force-pushed the cdleary/2024-11-21-get-rid-of-z3-extern branch from 6a3b468 to 5bacb25 Compare November 21, 2024 19:30
@cdleary cdleary marked this pull request as ready for review November 21, 2024 19:42
@hzeller
Copy link
Member

hzeller commented Nov 21, 2024

Given that we want to use MODULE.bazel at some point, I think I'd avoid patching external cc_library() targets to avoid too much local modifications.

But I am wondering if I can convince the external Verible maintainer to work on a weekend hack to move everything down a directory in the upstream project: common/ -> verible/common/.... @hzeller WDYT :) ?

@hzeller
Copy link
Member

hzeller commented Nov 21, 2024

I had a talk with the Verible maintainer ( 😃 ) and he agreed to put everything under a subdirectory upstream on the weekend.

@cdleary
Copy link
Collaborator Author

cdleary commented Nov 22, 2024

@meheff fixed this for z3 downstream, thanks @meheff !

@cdleary cdleary closed this Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants