kumquat-buildroot/support/scripts
Yann E. MORIN e49d4f0c37 support/scripts: prepare handling virtual packages in generated lists
Prepare to tell apart real packages from virtual packages.

Currently, the code implicitly recognises only real packages, and
discards virtual packages, because of the heuristic used to recognise
whether a symbol is a package:

  - for real package:
    - symbols  : BR2_PACKAGE_FOO
    - .mk files: foo.mk
  - for virtual packages:
    - symbols  : BR2_PACKAGE_HAS_FOO
    - .mk files: foo.mk

The current heuristic is to check for each symbol if a corresponding .mk
file exists, by stripping 'BR2_PACKAGE_' from the beginning of the symbol,
converting the result to lowercase, and checking if a .mk file exists.

So, as a side effect, it completely misses the virtual packages [*], which
is pretty nice since we get a list with only real packages that the user
can indeed select and see in the menuconfig.

[*] Except for 'cryptodev' and 'jpeg' which are both virtual packages and
normal packages. Except they are not normal packages, they are used to
display a choice of the implementation to use. This case will be fixed in
follow-up patches.

Since we'll soon need to also output the table of virtual packages, we
need to teach the _is_package() function to recognise them as well.

This patch is the first step into that direction: it introduces a new
function _is_real_package() that is just a wrapper to _is_package(), which
gains a new parameter, being the type of packages to filter on.

No behavioural change is made in this patch, it is just a preparatory
patch.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-06-08 17:08:36 +02:00
..
apply-patches.sh apply-patches.sh: make scan_patchdir work recursively 2014-02-08 22:26:16 +01:00
build-ext3-img support: move scripts/ to a new support/ directory 2011-09-17 08:14:11 +02:00
check-kernel-headers.sh support/check-kernel-headers: fix old custom toolchains without -print-sysroot 2014-04-09 01:38:10 +02:00
eclipse-register-toolchain eclipse support: document script and add checks 2013-01-14 21:45:09 +01:00
gen-manual-lists.py support/scripts: prepare handling virtual packages in generated lists 2014-06-08 17:08:36 +02:00
graph-build-time support/graphs: fix comparisons agains None 2014-04-14 22:50:24 +02:00
graph-depends graph-depends: rename the mode constants 2014-06-08 16:43:27 +02:00
kconfiglib.py manual: fix manual generation in preparation for BR2_EXTERNAL support 2013-12-08 22:32:02 +01:00
mkmakefile Makefile: fix out-of-tree builds with multiple targets with 'all' 2013-11-06 23:24:47 +01:00
mkusers support/mkusers: fix warnings when adding a new user 2014-04-05 18:39:16 +02:00
pkg-stats pkg-stats: fix whitespaces 2014-05-15 23:38:20 +02:00
readme.kconfiglib support: add kconfiglib python module 2013-05-04 12:27:00 +02:00
scancpan scancpan: sort dependencies 2014-05-18 23:54:09 +02:00
setlocalversion setlocalversion: sync with Linux kernel version (2.6.34) 2013-09-04 11:58:12 +02:00
xorg-release scripts: xorg-release: handle case when version needs downgrade 2014-02-04 10:32:11 +01:00

Readme
======

Kconfiglib
----------

This python module, developped by Ulf Magnusson and released under the ISC
license, is fetched from:

https://github.com/ulfalizer/Kconfiglib
commit: 02103fba9ae32a78291af53e50ee5d4bb3f69c1e

Kconfiglib license
~~~~~~~~~~~~~~~~~~

License (ISC)

Copyright (c) 2011-2013, Ulf Magnusson <ulfalizer@gmail.com>

Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.