Skip to content

Expand tree artifacts in textual_hdrs in generated module maps - #787

Open
fmeum wants to merge 1 commit into
bazelbuild:mainfrom
fmeum:textual-hdrs-tree-expansion
Open

Expand tree artifacts in textual_hdrs in generated module maps#787
fmeum wants to merge 1 commit into
bazelbuild:mainfrom
fmeum:textual-hdrs-tree-expansion

Conversation

@fmeum

@fmeum fmeum commented Jul 17, 2026

Copy link
Copy Markdown
Collaborator

Tree artifacts in a cc_library's textual_hdrs end up in the generated module map as a single header entry with the directory's path, which fails to parse (error: header '<dir path>' not found), instead of one textual header entry per contained file. hdrs and srcs already expand tree artifacts via the module map action's tree expander; this applies the same expansion to the public_textual_headers bucket.

Tree artifacts in a cc_library's textual_hdrs ended up in the generated
module map as a single header entry with the directory's path, which
fails to parse ('header ... not found'), instead of one textual header
entry per contained file like for hdrs and srcs.

@trybka trybka left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

good catch!

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.

2 participants