On Wed, Sep 15, 2010 at 02:51:40PM +0200, Michael Olbrich wrote:
> - some of the scripts provide functions used by other scripts. The
> dependencies have to be checked carefully.
> - not everything are function definitions. There might be unexpected side
> effects if the scripts are sourced later or multiple times.
>
> And will this be enough? Is the 32k limit for exec only or for running
> shells as well? Some of scripts are quite large.
I'll check, however size of exported functions is currently 45k, which is
quite a lot.
> This should be transparent for the make files. maybe wrapper functions:
>
> foo() {
> source ..../foo.sh # provies 'real' foo()
> foo "$@"
> }
>
> or something like that?
Could be. My idea was to leave functions needed for both makefiles
and scripts as they are and modify those used in get, prepare, extract,
compile, install and targetinstall stages as they occupy wast majority
of environment space. Then makefile rules can remain untouched, only
scrips patch will be added to $PATH (eventually modify makefiles to
contain absolute path).
Currently these functions are stored one per file anyway and exceptions
can be handled by adding helper function with parameter, for example
scripts/lib/ptxd_make_world_install.sh contains
ptxd_make_world_install
ptxd_make_world_install_unpack
ptxd_make_world_install_pack
ptxd_make_world_install_post
which could be then called as
ptxd_make_world_install
ptxd_make_world_install unpack
ptxd_make_world_install pack
ptxd_make_world_install post
ladis
--
ptxdist mailing list
ptxdist@pengutronix.de
