Skip to content

Move //:config to implementation_deps to prevent header collision#229

Merged
danilak-G merged 1 commit intogoogle:mainfrom
UebelAndre:config
Mar 6, 2026
Merged

Move //:config to implementation_deps to prevent header collision#229
danilak-G merged 1 commit intogoogle:mainfrom
UebelAndre:config

Conversation

@UebelAndre
Copy link
Contributor

Snappy's //:config target exposes config.h via hdrs and defines HAVE_CONFIG_H. Whenever //:snappy is in the dependency graph of any other cc_* target it results in snappy's config.h being added as an available header to compile actions. This leads to a header collision and breaks consumers. By moving //:config to implementation_deps the header is not propagated and the collision is avoided.

@UebelAndre
Copy link
Contributor Author

@danilak-G I don't think this change would negatively impact Google as I don't expect the generated config.h file to be something consumers of //:snappy directly consume.

@danilak-G danilak-G merged commit 6281a07 into google:main Mar 6, 2026
24 checks passed
@UebelAndre UebelAndre deleted the config branch March 6, 2026 22:34
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