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>
Sun Jun 13 23:38:37 2010 +0200 (2010-06-13)
changeset 1983 198a5a6e5239
parent 1512 439a6b292917
child 2564 5d4e91c0343e
permissions -rw-r--r--
cc/gcc: baremetal requires a two-pass process

Here, we implement a highly ugly hack. I'm not proud of that one...

To build the libstdc++ library, the compiler requires the C library. In
case we build for non-baremetal, this is normally handled by the final
step, later.

But in the case of bare-metal, we never go through the final step (because
it does not work, and it seems complex enough to make it work), so the
baremetal compilers are issued out of the core step. 
     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