Skip to content

snippets: Organize snippets based on generality and vendors specific snippets #93332

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

nashif
Copy link
Member

@nashif nashif commented Jul 18, 2025

  • scripts: snippets: cmake-out argument is needed
  • snippets: Organize snippets based on generality and vendors specific snippets

nashif added 2 commits July 18, 2025 08:40
Calling snippet.py script without any argument generates an error,
cmake-out is required, so make it mandatory.

Signed-off-by: Anas Nashif <[email protected]>
Snippets ideally should be general purpose and not limited to vendors or
specific boards. To distinguish between general snippets that can be
used in association with any target and those that are vendor specific,
create one more level and organize by vendors and put general ones under
generic.

Signed-off-by: Anas Nashif <[email protected]>
@nashif nashif force-pushed the topic/snippet/001 branch from cb7b635 to 2a37146 Compare July 18, 2025 13:01
Copy link

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.

1 participant