scripts: add "FILE" and "CFG" debug levels.
I ran into some minor difficulties looking through the build log for a
particular file: I wasn't interested in seeing it unpacked, but only
when it is built or installed. Adding these two levels allows me to
differentiate between those cases.
[Yann E. MORIN: Those are blind log levels, and are used only to search
in the build-log afterward.]
Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
1 This is a somewhat ordered TODO list:
5 - update versions for every tools...
7 - update and/or upgrade all samples
12 - update newlib (for enhanced bare metal)
13 - confirm existing implementation on targets other than AVR32
14 - try to make it generic, will help for uClibc++
18 - Cygwin target (needs newlib)
19 - so we can build toolchains that generate code for Windows/Cygwin
22 - so we can build toolchains that run natively under Windows/Cygwin
25 - so we can build toolchains that generate code for Windows/Win32
28 - so we can build toolchains that run natively under Windows/Win32
29 (without requiring Cygwin)
35 - check whether we can use newlib under uClinux (?)