TODO
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Tue Oct 16 20:57:44 2012 +0200 (2012-10-16)
changeset 3079 37831a33e07e
parent 1731 648fcf1f4568
child 3306 80e46e644bc0
permissions -rw-r--r--
kernel/linux: fix using custom location

Currently, extract and patch are skipped as thus:
- using a custom directory of pre-installed headers
- a correctly named directory already exists

Otherwise, extract and patch are done.

The current second condition is wrong, because it allows the following
sequence to happen:
- a non-custom kernel is used
- a previous build only partially extracted the non-custom sources
- that p[revious build broke during extraction (eg. incomplete tarball...)
- a subsequent build will find a properly named directory, and will
thus skip extract and patch, which is wrong

Fix that by following the conditions in this table:

Type | Extract | Patch
----------------------+---------+-------
Pre-installed headers | N | N
custom directory | N | N
custom tarball | Y | N
mainstream tarball | Y | Y

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: David Holsgrove <david.holsgrove@xilinx.com>
     1 This is a somewhat ordered TODO list:
     2 
     3 Recurring 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 (?)