Improve VSCode configuration for ICU4C build and test
For sample files in /docs/ide4c/vscode/ :
Set intltest's Current Working Directory to enable finding resources.
Make running all tests the unit-testing default.
Add c_cpp_properties.json, primarily for the includePath settings. [Linux: done. Others: not yet.]
Change max load-average from 90 to 20. (90 makes my laptop unusable during build. "Load average" is not "CPU usage percentage".)
Load average takes a while to respond, specify -j24 to always limit parallel jobs to a maximum of 24.
Document the adjustments that can be made in the README.
Skip the json files when checking for copyright notices. Pure json does not permit comments, so c_cpp_properties.json cannot have comments.
I suggest we mark it as fixed, and reopen a new ticket for any further configuration improvements.
There is a commit on this ticket shipping in ICU 68. Should the ticket be marked as fixed with fix version 68.1?
Passed on to : I currently only have access to Linux, so I can’t really take this further.
I do think -j24 and -l20 is still way too high as defaults. I kept them high because it used to be -l90, however it was set to -l90 due to a misunderstanding of what “load level” means. (I think they were going for 90% CPU usage.)
[I think 8 or 12 cores might be fairly common these days. I might at some point do some experimenting to see how long builds take on an 8 core and a 12 core machine for various -j settings, and how high each manages to push the load levels. In the meantime, I’m still happy considering this bug “closed” for Linux.]
I’ve submitted the changes for Linux - does someone want to take over this ticket for Windows/Mac?
also mentioned he could try things out on a Mac.