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 Jan 17 23:06:02 2010 +0100 (2010-01-17)
changeset 1740 c57458bb354d
parent 1512 439a6b292917
child 2564 5d4e91c0343e
permissions -rw-r--r--
configure: do not require hg when configuring in an hg clone

When configuring in an hg clone, we need hg to compute the version string.
It can happen that users do not have Mercurial (eg. if they got a snapshot
rather that they did a full clone). In this case, we can still run, of
course, so simply fill the version string with a sufficiently explicit
value, that does not require hg. The date is a good candidate. 
     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