openframeworks / openframeworks/openFrameworks
buildAllExamples script should not error out on first failed compilation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
Hi!
The buildAllExamples script should imo not exit when an example compilation fails, but store the example ID (and maybe error) and continue on, and at the end print a list of failed examples.
This would also be nifty w.r.t to automated testing - a CI server could directly call this script and all examples would be tested even if, e.g., the glnfoExample fails. Currently I run a modified version of this script while playing with Jenkins - just commented out the "exit".
Thoughts, @arturoc , @benben, @underdoeg?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the buildAllExamples script and inspect how it handles a failed compilation, especially the current exit path. Done means compilation attempts continue after failures and the script prints the failed example IDs, with any available errors, at the end.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100