You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have not updated pigweed for about 6 months due to the dropped support of python 3.9 (and ubuntu 20.04 only had that one).
Changes
pigweed update
WriteLine signature changed for pw_sys_io from const std::string_view& to just std::string_view
SLC generation failed and I am unsure why. Apparently prepending /usr/bin to PATH makes it use the right python and I do not fail with a jinja2 ModuleNotFound error
pigweed brings the clang-format and since that version changed, I did a zap regen to update file formatting for checked in generated files
Boringssl started to fail on connect.c on a cast of functions. Unsure why this fails only now, assuming clang is more strict, however that cast seems to be on purpose and borigssl explicitly tries to disable that warning but for MSVC only. I added the disable in the build.gn for boringssl itself.
added dependency from PlatformConfig to ICD configuration since it looks that there are situations (at least for silabs) where ICD configuration is loaded from platform configuration.
For OpenIOT added dependency on openiotsdk_buildconfig to the platform buildconfig
Adding a check for the PW_ENVIRONMENT_ROOT variable gn_silabs_example.sh was not needed in the end?
@jmartinez-silabs it is ok in CI because CI on the silabs image does not have a PW_ENVIRONMENT_ROOT set. it would be required for people testing in the vscode (or any custom local environment that uses it).
Q: it looks like there's a fair number of formatting changes. They look reasonably/ better, but is that going to mess stuff up for folks when they build products with zap files that aren't in the SDK?
Q: it looks like there's a fair number of formatting changes. They look reasonably/ better, but is that going to mess stuff up for folks when they build products with zap files that aren't in the SDK?
The reason for them is that we use clang-format from pigweed when formatting stuff with zap-regen (logic here was to have a clang-format that works on both linux and darwin the same ... and pigweed one is a fixed version).
I don't think others will be affected: this is strictly SDK generated files and all the rest of the files are restyle.io or not at all (whatever others are using)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We have not updated pigweed for about 6 months due to the dropped support of python 3.9 (and ubuntu 20.04 only had that one).
Changes
const std::string_view&to juststd::string_view/usr/binto PATH makes it use the right python and I do not fail with ajinja2 ModuleNotFounderrorconnect.con a cast of functions. Unsure why this fails only now, assuming clang is more strict, however that cast seems to be on purpose and borigssl explicitly tries to disable that warning but for MSVC only. I added the disable in the build.gn for boringssl itself.-c(and [Tooling] -fsyntax-only adjuster: remove -c and -S llvm/llvm-project#101103 says that-Sis also in the same category). Added code in our clang-tidy runner to auto-skip -c and -S arguments..template MemberCall(...calls. Updated tv code to do this.ConnnectiontoConnection(found while fixing java call signatures)