Hi,
On Wed, Jan 23, 2013 at 01:28:26PM +0100, Alexander Stein wrote:
> On Wednesday 23 January 2013 12:26:24, Michael Olbrich wrote:
> > What's the usecase for this? This are a lot of options and hard to
> > maintain. And the plugins are so small, that I don't think it's worth it to
> > save the space.
>
> That's exactly the use case. On that particular board we don't have much
> flash memory available, so even reducing about 1,4 MiB is essential in that
> case.
> You can at least get a list of the modules when the package is installed
> using this shell command:
> > for mod in platform/packages/lighttpd-1.4.31/usr/lib/lighttpd/*.so; do
> > MOD=$(basename $mod); echo ${MOD/.so/}; done
> This could be a starting point to create e.g. a lighttpd_modules.in by a
> script which includes this options.
I've pushed my lighttpd rework that I've been working on for some time. You
can now explicitly select some modules (those that require extra
dependencies etc.). For the rest there is a string to add them manually.
The list will be added for loading to the config file, and optionally used
to only install these modules.
Does this work for you?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
[email protected]
