simbit18 commented on PR #18500:
URL: https://github.com/apache/nuttx/pull/18500#issuecomment-4011266295
Hi everyone!
Possible solution (to be verified, of course) to test and not modify the
existing process.
Currently, GitHub jobs use static .dat files contained in the ci/testlist
directory for compilation with Make or CMake.
Would it be possible to create a folder outside the NuttX tree, for example
workspace/citest, and then have a tool (select.py or other) that generates one
or more .dat files (using the current logic) containing what we want to compile
and a .json file to pass to the dedicated job on GitHub?
The job will read the .json file with the names of the .dat files that we
will pass to ./cibuild.sh as is currently the case.
./cibuild.sh -c -A -N -R -S workspace/citest/${{matrix.boards}}.dat
The folder outside the nuttxworkspace/citest tree could also be useful for
locally testing boards under development or other things, manually adding the
file with the boards to build.
Questions:
Will this system on GitHub only work for Linux (Docker)?
How can we know if it is possible to build a board on macOS, MSVC, or MSYS2
? Will these jobs be started in any case?
What should we do if there are changes to a board and other types, such as
nuttx/drivers? What should the tool generate?
Of course, the questions don't end there! But I have to preserve my brain
cells :)
--
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]
