add cxx oot build test script to ci

[trns1997]

Note: Please adhere to Contributing Guidelines.

Summary

This PR introduces a new CI test for out-of-tree builds to prevent regressions in the make export workflow.
Specifically, it adds a test-oot-build.sh script that:

• Builds NuttX using a selected configuration.
• Runs make export to generate the export package.
• Copies the nuttx-export to the oot build project.
• Verifies that compilation and linking succeed.

Issue: #17016
Provides: apache/nuttx-apps#3185
Depends-on: #16976

Impact

• Please fill in Impact section.

Testing

• Please fill in Testing section.

[trns1997]

I’ve added a hellocpp out-of-tree CMake project based on #16970 and a test-oot-build.sh script.

The script does the following:

• Configures a board and builds NuttX.
• Runs make export to generate the export tarball.
• Copies and extracts the export package into the hellocpp folder.
• Builds the out-of-tree CMake project to verify that compilation and linking succeed.

It currently works locally, but I’d like some guidance on CI integration:

• Should I add a step in tools/testbuild.sh to call this script?
• CI currently runs builds for all boards listed under tools/testlist/. Do we also want to run this out-of-tree export test for all boards, or should we select a single representative board/config to keep CI runtime reasonable?

Looking for feedback on where this test should live in the CI pipeline and which boards we should cover.

[trns1997]

I’ve added a hellocpp out-of-tree CMake project based on #16970 and a test-oot-build.sh script.

The script does the following:

* Configures a board and builds NuttX.

* Runs make export to generate the export tarball.

* Copies and extracts the export package into the hellocpp folder.

* Builds the out-of-tree CMake project to verify that compilation and linking succeed.

It currently works locally, but I’d like some guidance on CI integration:

* Should I add a step in `tools/testbuild.sh` to call this script?

* CI currently runs builds for all boards listed under `tools/testlist/`. Do we also want to run this out-of-tree export test for all boards, or should we select a single representative board/config to keep CI runtime reasonable?

Looking for feedback on where this test should live in the CI pipeline and which boards we should cover.

ping @leducp i would like your input on this plz :)

[raiden00pl]

Should I add a step in tools/testbuild.sh to call this script?
CI currently runs builds for all boards listed under tools/testlist/. Do we also want to run this out-of-tree export test for all boards, or should we select a single representative board/config to keep CI runtime reasonable?

We need to conserve CI resources due to Apache Foundation restrictions, so one representative board is enough. In the future we can include tests for various host OSes (Mac, Windows) but for now Linux is probably enough?

I'm not sure where to run this script, probably we should add another job in the build workflow and call it directly: https://github.com/apache/nuttx/blob/master/.github/workflows/build.yml

tools/testbuild.sh is designed to work with <testlist-file> and in the case of your script, <testlist-file> is not used, so these two don't really fit together.

[leducp]

I’ve added a hellocpp out-of-tree CMake project based on #16970 and a test-oot-build.sh script.
The script does the following:

* Configures a board and builds NuttX.

* Runs make export to generate the export tarball.

* Copies and extracts the export package into the hellocpp folder.

* Builds the out-of-tree CMake project to verify that compilation and linking succeed.

It currently works locally, but I’d like some guidance on CI integration:

* Should I add a step in `tools/testbuild.sh` to call this script?

* CI currently runs builds for all boards listed under `tools/testlist/`. Do we also want to run this out-of-tree export test for all boards, or should we select a single representative board/config to keep CI runtime reasonable?

Looking for feedback on where this test should live in the CI pipeline and which boards we should cover.

ping @leducp i would like your input on this plz :)

Seems OK as a starter: having an export + OOT app build and linked to it is already years away from the current state :)

[trns1997]

Should I add a step in tools/testbuild.sh to call this script?
CI currently runs builds for all boards listed under tools/testlist/. Do we also want to run this out-of-tree export test for all boards, or should we select a single representative board/config to keep CI runtime reasonable?

We need to conserve CI resources due to Apache Foundation restrictions, so one representative board is enough. In the future we can include tests for various host OSes (Mac, Windows) but for now Linux is probably enough?

I'm not sure where to run this script, probably we should add another job in the build workflow and call it directly: https://github.com/apache/nuttx/blob/master/.github/workflows/build.yml

tools/testbuild.sh is designed to work with <testlist-file> and in the case of your script, <testlist-file> is not used, so these two don't really fit together.

Noted, i will treat this as a seperate test and add a new stage to build.yml for stm32f4discovery:cxx-oot-build :)

[acassis]

@trns1997 please add entry to cxx-oot-build board profile in the Documentation/ please explain the details to test it.

[trns1997]

@trns1997 please add entry to cxx-oot-build board profile in the Documentation/ please explain the details to test it.

Do you prefer a separate document or should I integrate it with an existing one? Like the cpp cmake out of tree example updated by @leducp recently?

[cederom]

Thank you @trns1997 :-) Please take a look at [1] [2] [3] and update git commit message and PR description to match requirements :-)

[1] https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md
[2] https://nuttx.apache.org/docs/latest/contributing/index.html
[3] https://nuttx.apache.org/docs/latest/contributing/coding_style.html

[acassis]

@trns1997 to test the Documentation:
$ cd Documentation
$ make html

[trns1997]

@xiaoxiang781216 can we rerun just the last stage or should we rerun the entire pipeline?

[simbit18]

@trns1997 Everything needs to be redone. Here, nuttx-apps does not have the latest updates.

nuttx/.github/workflows/build.yml

Line 42 in 6a57c56

# Fetch the source from nuttx and nuttx-apps repos

[simbit18]

@trns1997 Please, can you add tests done locally?
The cibuild-oot.sh script is missing the step where artifacts are stored.

you can see in this script testbuild.sh

nuttx/tools/testbuild.sh

Line 28 in d243322

if [ -z $ARTIFACTDIR ]; then

nuttx/tools/testbuild.sh

Line 397 in d243322

if [ ${SAVEARTIFACTS} -eq 1 ]; then

fix