EFR32: Fix ARM arch setup when setting efr32_board in GN args (#1978)

* EFR32: Fix ARM arch setup when setting efr32_board in GN args

Currently examples/lock-app/efr32/args.gni tries to set the
ARM architecture flags based on a condition:

if (efr32_family == "efr32mg12") {
  arm_float_abi = "softfp"
  arm_fpu = "fpv4-sp-d16"
} else if (efr32_family == "efr32mg21") {
  arm_float_abi = "hard"
  arm_fpu = "fpv5-sp-d16"
}

This isn't working if the board is set via GN args, which is preferred
over the environment variable. The reason is that this file is providing
the default arguments, and it's not possible to use the user arguments
to set the defaults. We want explicit args to take precedence, and this
is necessary for toolchain specific arguments to work.

Fix this by adding a way for platforms to provide a config file that
sets up the default ARM architecture flags (and which can account for
other platform specific arguments in doing so, such as efr32_board).

* Fix building for nRF5 via gn_build.sh

* Share the build_overrides

* Add efr32_sdk.gni back to build_overrides
16 files changed
tree: 07dce4f4b79fff1336893946c34128eff82c7099
  1. .devcontainer/
  2. .github/
  3. .vscode/
  4. autoconf/
  5. config/
  6. docs/
  7. examples/
  8. gn/
  9. integrations/
  10. scripts/
  11. src/
  12. third_party/
  13. tools/
  14. .chip-banner.txt
  15. .clang-format
  16. .default-version
  17. .default-version.min
  18. .dir-locals.el
  19. .editorconfig
  20. .gitignore
  21. .gitmodules
  22. .gn
  23. .prettierrc.json
  24. .pullapprove.yml
  25. .restyled.yaml
  26. .shellcheck_tree
  27. bootstrap
  28. BUILD.gn
  29. CODE_OF_CONDUCT.md
  30. configure.ac
  31. CONTRIBUTING.md
  32. gn_build.sh
  33. LICENSE
  34. Makefile-Android
  35. Makefile-bootstrap
  36. Makefile-Standalone
  37. Makefile.am
  38. README.md
  39. REVIEWERS.md
README.md

Connected Home over IP

Main Examples QEMU

What is Project Connected Home over IP?

Visit connectedhomeip.com to learn more.

Current Status of Project Connected Home over IP

The Zigbee Alliance officially opened the Project Connected Home over IP (Project CHIP) Working Group on January 17 and is in the process of drafting the specification.

The Project’s design and technical processes are intended to be open and transparent to the general public, including to Work Group non-members wherever possible. The availability of this GitHub repository and its source code under an Apache v2 license is an important and demonstrable step to achieving this commitment.

The Project endeavors to bring together the best aspects of market-tested technologies and to redeploy them as a unified and cohesive whole-system solution. The overall goal of this approach is to bring the benefits of the Project to consumers and manufacturers as quickly as possible. As a result, what you observe in this repository is an implementation-first approach to the technical specification, vetting integrations in practice.

How to Contribute

We would love for you to contribute to Project Connected Home over IP. Read our contribution guidelines here.

Building and Developing in Project

Instructions about how to build Project Connected Home over IP can be found here.

Directory Structure

The Connected Home over IP repository is structured as follows:

File / FolderContents
.default-versionDefault Project CHIP version if none is available via source code control tags, .dist-version, or .local-version
bootstrapGNU autotools bootstrap script for the Project CHIP build system
bootstrap-configureConvenience script that will bootstrap the Project CHIP build system, via bootstrap, and invoke configure
build/Build system support content and build output directories
BUILDING.mdMore detailed information on configuring and building Project CHIP for different targets
CODE_OF_CONDUCT.mdCode of Conduct for Project CHIP, and contributions to it
CONTRIBUTING.mdGuidelines for contributing to Project CHIP
CONTRIBUTORS.mdContributors to Project CHIP
docs/Documentation
examples/Example firmware applications that demonstrate use of Project CHIP technology
integrations/Third party integrations related to this project
integrations/docker/Docker scripts and Dockerfiles
LICENSEProject CHIP License file (Apache 2.0)
Makefile-AndroidConvenience makefile for building Project CHIP against Android
Makefile-StandaloneConvenience makefile for building Project CHIP as a standalone package on desktop and server systems
README.mdThis file
src/Implementation of Project CHIP
third_party/Third-party code used by Project CHIP
tools/Tools needed to work with the Project CHIP repo

License

Project CHIP is released under the Apache 2.0 license.