-
Notifications
You must be signed in to change notification settings - Fork 9
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
PR: RDKE-41 Enhance component versioning and standard build support #34
Conversation
…coupling the install directory restructuring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this cannot be a fork, contributing to this code is via branching the codebase only, and raising a ticket in the issue list, and using that as the branch name.
Generating a pull request to develop from the feature/ghxx_synopsis code change.
See -> https://github.com/rdkcentral/rdk-halif-device_settings/blob/main/CONTRIBUTING.md
Hi @Ulrond ,
Without forking and adding a commit; i'm not able to create a PR. |
@arun-madhavan-013 , |
ok you've been added to the project so you should be able to create a branch, but why is this change being added to this repo? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please arrange a call to discuss this.
Headerfiles are not fixed location, and they do not specify an included dir.
it's upto the project manifest and the .bb file to set the project requirements not this header file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not something that should be committed to the header file.
Enhance component versioning and standard build support by decoupling the install directory restructuring.
Problem:
How it helps:
Newly introduced pkg-config file will have the header component version and standard build flow can detect it.
when pkg-config is having 2.0.0
when pkg-config is having 1.0.8
When vendor or middleware component builds; it can do a standard find pkg-config step and get the respective header installation path provided by halif-devicesettings.pc even if it is non-standard location. This helps to decouple the compile flag modification required to match Problem statement 2 similar changes.
One-time change required in meta-rdk-halif-headers
Install the respective pkg-config file from meta-rdk-halif-headers recipe.