Monolithic zsh with an attitude

Monolithic zsh with an attitude

[Raúl Núñez de Arenas Coronado]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]

    Hello zsh-workers :)

    I need to build a monolithic zsh but I want it to have some
additional builtins, as the ones contained in the dynamic module
'mathfunc', for example.

    Obviously, if I use --disable-dynamic, none of these modules are
available, and 'configure' doesn't provide a way of choosing whether
the modules must be included in the monolithic zsh (that's obvious
too, and desirable).

    My question is: must (and safely can) I edit the appropriate
'.mdd' files to have some modules statically linked in my monolithic
zsh or is it dangerous?. I'm assuming that the way to have the
modules I need statically linked is editing the corresponding '.mdd'
file and changing the 'link' parameter (and maybe 'load' too).

    Am I wrong?

    Raúl

Re: Monolithic zsh with an attitude

[Bart Schaefer]

On Oct 28,  9:29pm, Raúl Núñez de Arenas Coronado wrote:
} 
} [...] 'configure' doesn't provide a way of choosing whether the
} modules must be included in the monolithic zsh (that's obvious too,
} and desirable).

If you read the INSTALL file, you'll find the answers you seek:

 The key to the module system is the file config.modules, created in
 the configuration process.  In the normal case that dynamic loading is
 available, all modules relevant to your configuration will be compiled
 and installed as separate files, so unless you want the modules to be
 loaded by default you don't need to do anything.  For a non-dynamic zsh,
 the default is to compile the complete, compctl, zle, computil, complist,
 sched, parameter, zleparameter and rlimits modules into the shell, and
 you will need to edit config.modules to make any other modules available.
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   

Re: Monolithic zsh with an attitude

[Raúl Núñez de Arenas Coronado]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

    Hello Bart :))

>} [...] 'configure' doesn't provide a way of choosing whether the
>} modules must be included in the monolithic zsh (that's obvious too,
>} and desirable).
>If you read the INSTALL file, you'll find the answers you seek:

    I'm afraid I didn't explained correctly O:)) I forgot to say that
the choice must be done *before* 'configure' is run if file editing
is involved, so it can be compiled on destination.

    But I suppose that if I include a copy of config.modules it won't
be overwritten by 'configure' (I think that config.modules has a
flag to achieve that...).

    Thanks a lot for your answer, anyway :)))

    Raúl