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
custom_targets.json and modular target board support packages #6581
Comments
@loverdeg-ep The current limitation, that the "custom_targets.json" must be at the root, is primarily an implementation limitation. You could "trick" the build system into thinking that it's at the root by:
I take it that this is almost a blocker for going to production? |
@theotherjimmy Not quite a blocker since we can work around it. |
@loverdeg-ep Yeah, It seems that custom target support is really needed for going to production, as you use it for the custom board you're making. I appreciate that you're pushing on it, as it frequently sees the least love. |
Internal Jira reference: https://jira.arm.com/browse/IOTCORE-323 |
@theotherjimmy, @trowbridgec We will be using the recommended workaround, but it would be nice the next time I chase my tail to find a @theotherjimmy All that being said, |
@loverdeg-ep The implementation that you outlined would work, and I would accept a PR that adds and implements a |
Good to know that something feels off to you. If you can put your finger on what that is, I would like to know it. |
TODO: Close once #9401 comes with 5.12. |
--custom-targets command line switch was delivered in #9401 so closing this issue. |
Description
@theotherjimmy @0xc0170
Background
Assume I create a custom target and want to use that target in multiple applications.
The most elegant approach I can think of with my limited understanding of the config system, would be to create a git repository that contains the following:
This repository would then be imported as a git submodule of any applications I develop for the board.
(or, if the application is hardware agnostic enough, I might create a new repository that includes both the application and BSP as git submodules)
Known Issues to using this approach:
Questions
What currently is the cleanest way to accomplish modular custom target support for an application?
What, if anything, could be done to 'enhance' custom target support?
The text was updated successfully, but these errors were encountered: