trns1997 opened a new issue, #17016: URL: https://github.com/apache/nuttx/issues/17016
### Is your feature request related to a problem? Please describe. In PR #16976, several issues were uncovered when using make export (exported content) together with CMake / out-of-tree builds, such as: - The missing gnu-elf.ld template caused make export to emit a “cannot stat …” error when CONFIG_LIBC_ELF was not enabled. - The exported startup/ directory (and/or crt0.o) might not be created correctly, leading to failures when using set -e in shell scripts. - Potential for multiple definition of symbols (e.g. __start) when using an export + CMake build, due to ambiguity in startup object selection. These kinds of regressions are subtle and may go unnoticed until someone tries an out-of-tree build (e.g. using the exported NuttX package with custom userspace or external apps). ### Describe the solution you'd like ### Proposal Introduce a CI test (or tests) which perform out-of-tree build(s) using the exported package + CMake (or other build systems as applicable) with a simple example (e.g. “Hello World” or minimal NuttX + user app) to verify that the exported artifacts are usable and complete. @leducp has already done a big chunk fo the work here https://github.com/apache/nuttx/pull/16970. The idea is to automate this procedure to add a build test as mentioned: https://github.com/apache/nuttx/pull/16976#issuecomment-3257709832. ### Goals - Prevent future regressions similar to the ones described above. - Ensure make export produces a package that can actually be built out-of-tree, including correct startup/, linker scripts, necessary headers, scripts, etc. - Detect missing files, wrong assumptions (e.g. that gnu-elf.ld always exists), or divergence between in-tree vs out-of-tree build behavior. - Ideally catch compile/link errors (or missing files) early in CI. ### Describe alternatives you've considered _No response_ ### Verification - [x] I have verified before submitting the report. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
