Skip to content

Fix --without with slcp files#449

Open
Jean-Francois Penven (jepenven-silabs) wants to merge 1 commit intomainfrom
no_jira_fix_build.sh
Open

Fix --without with slcp files#449
Jean-Francois Penven (jepenven-silabs) wants to merge 1 commit intomainfrom
no_jira_fix_build.sh

Conversation

@jepenven-silabs
Copy link
Contributor

Issue Link:
--without doesn't work if you're building a slcp file with the build.sh script. It does work if you're building a solution,
Description of Problem/Feature:

Description of Fix/Solution:
Copy paste the logic for solution (slcw ) with the slcp use case

Testing Done:

It did build locally with the release branch should work with this one as well

APP_WITHOUT_ARG=$(build_without_arg "$WITHOUT_APP_COMPONENTS")
# Generate .slcp projects
run_slc_generate_with_retry generate -d $OUTPUT_DIR $PROJECT_FLAG $SILABS_APP_PATH --with $SILABS_BOARD $CONFIG_ARGS --generator-timeout=3500 -o makefile
run_slc_generate_with_retry generate -d "$OUTPUT_DIR" --sdk-package-path "$SISDK_ROOT" --sdk-package-path "$EXTENSION_DIR" --sdk-package-path "$WISECONNECT3_DIR" $PROJECT_FLAG "$SILABS_APP_PATH" $APP_WITH_ARG $APP_WITHOUT_ARG $CONFIG_ARGS --generator-timeout=180 -o makefile
Copy link
Contributor

@Sarthak-Shaha sarthak shaha (Sarthak-Shaha) Jan 26, 2026

Choose a reason for hiding this comment

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

The build systems on main(SLC spec 12) vs release_2.8 (SLC spec 14) branches are different,
The above changes show use of --sdk-package-path, is a slc spec 14 feature.
Perhaps update PR to target release_2.8?

Choose a reason for hiding this comment

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

Goal is to merge this PR on main so that future work will have this fix. If we need to wait for main to be on part with release_2.8 then we can wait. But I don't see why future development should target a previous release branch...

Choose a reason for hiding this comment

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

Agreed, then it should be good to go after the merge of release_2.8-1.5 back to main

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.

2 participants