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

Fix include paths for CGo deps in external repositories #3115

Merged
merged 1 commit into from
Apr 15, 2022

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Apr 12, 2022

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

A CGo-generated header file from any repository, external or main, must
always be includeable via its path relative to its repository root.
Previously, this was not true for CGo targets in external repositories,
which required an additional external/<repo name>/ prefix, thus
breaking references within the external repository.

Which issues(s) does this PR fix?

Fixes #3109

Other notes for review

A CGo-generated header file from any repository, external or main, must
always be includeable via its path relative to its repository root.
Previously, this was not true for CGo targets in external repositories,
which required an additional `external/<repo name>/` prefix, thus
breaking references within the external repository.

Fixes bazelbuild#3109
@fmeum fmeum force-pushed the 3109-fix-external-include-paths branch from 76c459c to 4a6060f Compare April 15, 2022 14:16
@linzhp linzhp merged commit 4d3a900 into bazelbuild:master Apr 15, 2022
@fmeum fmeum deleted the 3109-fix-external-include-paths branch April 15, 2022 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] CGO target headers not added to search paths when imported as external repository
3 participants