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>
Sat Jun 04 19:17:26 2011 +0200 (2011-06-04)
changeset 2506 2ab553e37517
parent 1512 439a6b292917
child 2564 5d4e91c0343e
permissions -rw-r--r--
configure: rationalise error messages with meaningful texts

Currently, error messages just state the obvious: a required
component is required. While in some cases, there is not much
else to say, in some other cases we could tell much more.

For example, a missing libstdc++ means no static toolchain.

Also, format error and warning messages in a similar fashion,
with a {error,warning} intro, followed by the message specified
by the caller.

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