This changes the order of the script to be:
Necssary bring up tasks
Setting variables to control rest of system intialization
Sourcing shared functions
Setting script functions
Doing the work of bringing the system up
Signed-off-by: Ian Leonard <antonlacon@gmail.com>
When building lirc after alsa-utils, the following unwanted alsa libraries are built by lirc:
NEW FILE Delta: 10,536 devel-20190115185543-5767941: 10,536 devel-20190115133317-5767941: n/a /usr/lib/lirc/plugins/alsa_usb.so
NEW FILE Delta: 19,176 devel-20190115185543-5767941: 19,176 devel-20190115133317-5767941: n/a /usr/lib/lirc/plugins/audio_alsa.so
Using $id to get the rcX device name from the SUBSYSTEMS match,
as used by the upstrem v4l-utils udev rule, is easier and more
stable than using IMPORT{parent}, which needs to transmit info across
two levels (rcX->inputY->eventZ) and breaks with kernel 4.20.
Instead of running a shell script to check for the existance of
/storage/.config/rc_maps.cfg we can use the builtin udev TEST
function.
Also it's better to use ENV variables prefixed with a dot as
they are used only locally in the udev rule file and don't need
to be persisted in the udev database or exported to external tools.
Signed-off-by: Matthias Reichl <hias@horus.com>
Packages referencing variables defined in setup_toolchain such as CC, CXX,
AR, CFLAGS, LDFLAGS, HOST_CC etc. etc. must only reference these variables in
pre_build()/pre_configure()/pre_make() etc. functions, as the variables will not
be available when the package is sourced, but will be available after the call
to setup_toolchain() from scripts/build.
