commit | 19e0c40685b4088e553479231d3f93d29928452e | [log] [tgz] |
---|---|---|
author | Michael Spang <spang@google.com> | Wed Aug 05 11:44:14 2020 -0400 |
committer | GitHub <noreply@github.com> | Wed Aug 05 11:44:14 2020 -0400 |
tree | 07dce4f4b79fff1336893946c34128eff82c7099 | |
parent | 3a23f738ec092e0ef46e47ac8ca55d1ffc89518f [diff] |
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
Visit connectedhomeip.com to learn more.
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.
We would love for you to contribute to Project Connected Home over IP. Read our contribution guidelines here.
Instructions about how to build Project Connected Home over IP can be found here.
The Connected Home over IP repository is structured as follows:
File / Folder | Contents |
---|---|
.default-version | Default Project CHIP version if none is available via source code control tags, .dist-version , or .local-version |
bootstrap | GNU autotools bootstrap script for the Project CHIP build system |
bootstrap-configure | Convenience script that will bootstrap the Project CHIP build system, via bootstrap , and invoke configure |
build/ | Build system support content and build output directories |
BUILDING.md | More detailed information on configuring and building Project CHIP for different targets |
CODE_OF_CONDUCT.md | Code of Conduct for Project CHIP, and contributions to it |
CONTRIBUTING.md | Guidelines for contributing to Project CHIP |
CONTRIBUTORS.md | Contributors 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 |
LICENSE | Project CHIP License file (Apache 2.0) |
Makefile-Android | Convenience makefile for building Project CHIP against Android |
Makefile-Standalone | Convenience makefile for building Project CHIP as a standalone package on desktop and server systems |
README.md | This 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 |
Project CHIP is released under the Apache 2.0 license.