Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
TODO
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Dec 23 20:43:32 2010 +0100 (2010-12-23)
changeset 2307 2efd46963086
parent 1512 439a6b292917
child 2564 5d4e91c0343e
permissions -rw-r--r--
buildtools: move to working directory

There is absolutely *no* reason for the buildtools (wrappers to gcc, g++,
as, ld... for the local machine) to be in the toolchain directory. Moreover,
they are removed after the build completes.

Move them out of the toolchain directory, and into the build directory (but
yet the part specific to the current toolchain). This means we no longer
need to explicitly remove them either, BTW, but we need to save/restore them
for the restart feature.

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 (?)
crosstool-ng