TODO
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Mar 20 00:02:21 2011 +0100 (2011-03-20)
changeset 2339 730e2d63296b
parent 1512 439a6b292917
child 2564 5d4e91c0343e
permissions -rw-r--r--
scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 This is a somewhat ordered TODO list:
     2 
     3 Recuring tasks:
     4 
     5 - update versions for every tools...
     6 
     7 - update and/or upgrade all samples
     8 
     9 
    10 Non-recurring tasks:
    11 
    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++
    15 
    16 - multilib
    17 
    18 - Cygwin target (needs newlib)
    19   - so we can build toolchains that generate code for Windows/Cygwin
    20 
    21 - Cygwin host
    22   - so we can build toolchains that run natively under Windows/Cygwin
    23 
    24 - mingw32 target
    25   - so we can build toolchains that generate code for Windows/Win32
    26 
    27 - mingw32 host
    28   - so we can build toolchains that run natively under Windows/Win32
    29     (without requiring Cygwin)
    30 
    31 - uClibc++
    32   - see newlib, above
    33 
    34 - uClinux
    35   - check whether we can use newlib under uClinux (?)