Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt a Project-consistent Two-level #include Directive Name Pattern for the System Layer Library #221

Merged

Conversation

gerickson
Copy link
Contributor

Problem

Currently most of the system layer library headers do not follow a two-level include name pattern used by the rest of the project.

Summary of Changes

Adopts a two-level #include directive name pattern for system layer library headers.

Fixes #220

@woody-apple
Copy link
Contributor

@rwalker-apple ?

@sagar-apple
Copy link
Contributor

LGTM, but just curious, is reducing the -I directives the primary purpose of this?

@gerickson
Copy link
Contributor Author

gerickson commented Apr 2, 2020

LGTM, but just curious, is reducing the -I directives the primary purpose of this?

Not reducing per se but making those that are required consistent from subsystem and module to subsystem and module. If reduction happens as a side-effect, that's a bonus.

When this project is closer to done, my goal for a consumer of the SDK would be to add two compiler / linker options to his / her command line for headers and libraries:

  • -I<path to CHIP public API include headers>
  • -L<path to CHIP public API libraries>

and for every public API header for the CHIP SDK to be of the form:

Less Ideal

#include <<CHIP Subsytem>/HeaderName.{h,hpp}>

More Ideal

#include <chip/<CHIP Subsytem>/HeaderName.{h,hpp}>

@rwalker-apple
Copy link
Contributor

lgtm

we had undone this because we didn't have "dist" in the make system at project kickoff

@gerickson
Copy link
Contributor Author

@hawk248 or @jelderton?

Copy link

@hawk248 hawk248 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@woody-apple woody-apple merged commit c77aaf2 into project-chip:master Apr 2, 2020
mkardous-silabs referenced this pull request in mkardous-silabs/connectedhomeip Nov 2, 2022
…aviour with the app UI (project-chip#23331)" from silabs to silabs_1.0

Merge in WMN_TOOLS/matter from cherry-pick/fix_autorelock to silabs_1.0

Squashed commit of the following:

commit 76df32b2d0e6c627545656d9e675c33825f2dab9
Author: jmartinez-silabs <[email protected]>
Date:   Wed Oct 26 17:16:25 2022 -0400

    [EFR32] Link the door lock relock behaviour with the app UI (project-chip#23331)

    * Make the relock callback weak, implement it on the app side and link our app ui

    * address PR comments, Create a new functions that deal with the cluster and calls the application callback
rerasool added a commit to SiliconLabs/matter that referenced this pull request Nov 2, 2022
…k relock behaviour with the app UI (project-chip#23331)" from silabs to silabs_1.0

Merge in WMN_TOOLS/matter from cherry-pick/fix_autorelock to silabs_1.0

Squashed commit of the following:

commit 76df32b2d0e6c627545656d9e675c33825f2dab9
Author: jmartinez-silabs <[email protected]>
Date:   Wed Oct 26 17:16:25 2022 -0400

    [EFR32] Link the door lock relock behaviour with the app UI (project-chip#23331)

    * Make the relock callback weak, implement it on the app side and link our app ui

    * address PR comments, Create a new functions that deal with the cluster and calls the application callback
Sarthak-Shaha pushed a commit to Sarthak-Shaha/connectedhomeip_silabs that referenced this pull request Jan 28, 2025
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.

Ensure System Layer Library #include Directives Follow Two-level Pattern
7 participants