-
Notifications
You must be signed in to change notification settings - Fork 78
fix(workflows): Drop GEN & Add support for debian, buildroot #129
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
Conversation
|
@makohoek for reviews |
- GitHub pages are introduced for customers/ developers to get access the latest bleeding-edge documentation - DEVFAMILY=GEN is not used in production by any OS & hence contains irrelevant information [1]. So, stop building it as a part of CICD. [1]: https://texasinstruments.github.io/processor-sdk-doc/processor-sdk-linux-GEN/esd/docs/10_01/linux/index.html Signed-off-by: Chirag Shilwant <[email protected]>
- Add support for building buildroot for AM62X Signed-off-by: Chirag Shilwant <[email protected]>
- Add support for building debian for AM62X, AM62PX & AM64X Signed-off-by: Chirag Shilwant <[email protected]>
|
@cshilwant , Would it make sense to completely eliminate the 'General' variable? There are many files which have this variable so it would make sense to remove them in one swoop because otherwise context might be lost? |
@AashvijShenai Eliminating GEN config might need more internal discussion. This PR was intended to avoid it from building in GitHub pages CICD as it contains information that's irrelevant for customers/ developers. |
|
Well, hold on. @praneethbajjuri I've been meaning to ask you about the GEN and CORESDK DEVFAMILY configs, as they never made any sense on their own and I had never seen a deployment of them. Are these being used anymore? Are we safe to prune them? We should also prune any ifconfig directives using parameters listed under these configs. |
|
Ok to prune gen. |
|
Alright. We'll merge the CI cleanup now and have a followup to drop the config and modify the source. |
Uh oh!
There was an error while loading. Please reload this page.