diff options
| author | emilylange <git@emilylange.de> | 2025-08-11 04:56:44 +0200 |
|---|---|---|
| committer | emilylange <git@emilylange.de> | 2025-08-11 05:02:20 +0200 |
| commit | 27eac9f0b8e5632dc55b1eee8f89b55b56c4075f (patch) | |
| tree | 10b027793ae258c8884f04bb52cbcc170b1f9392 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 069fd014f2e9fe87dda611c348fb650158e43066 (diff) | |
python3Packages.home-assistant-chip-wheels: fix building with newer gn
This fixes the following error caused by https://gn-review.googlesource.com/c/gn/+/18820
and the gn bump in b59bfde89d116c180cc20962fdecbf40d92f8ce7 by
backporting https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/300272
~~~
Running phase: configurePhase
gn flags: chip_project_config_include_dirs=\[\"//..\"\] chip_crypto=\"openssl\" [...]
generated_file("$target_name._includes") {
^-----------------------------------------
Two or more targets generate the same output:
protocol_buffer/gen/third_party/pigweed/repo/pw_chrono/protos.proto_library/includes.txt
This is can often be fixed by changing one of the target names, or by
setting an output_name on one of them.
Collisions:
//third_party/pigweed/repo/pw_chrono:protos._includes(//build/toolchain/custom:custom)
~~~
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions