Re: Static link of curses module

[Bart Schaefer <schaefer@brasslantern.com>]

On Sep 27,  4:28pm, Peter Stephenson wrote:
}
} Typically, you'd do this by editing config.modules rather than the .mdd

config.modules is generated from the .mdd and then is what gets used at
build time, so yeah.

} I'm not sure how this is supposed to work. I can see the module being
} registered automatically, but I don't see any evidence that there
} was ever a mechanism for running the request "load_module" based on
} load=yes.

Yeah, I don't think that was ever what it was intended to mean.  I think
the intent was that if the module has autoloads, then you don't have to
declare them with "zmodload -a".  It doesn't imply that load_module()
is actually called.

Look at the modules that have "load=yes" in the default .mdd file:

rlimits
sched
parameter
termcap
terminfo
zutil
(plus several in Zle)

Those all have autofeatures declared.  Then look at curses.mdd -- it
has "autobins" instead.  No other .mdd file has "autobins".

I think curses.mdd just got overlooked when we converted to the features
mechanism.  Try this?


diff --git a/Src/Modules/curses.mdd b/Src/Modules/curses.mdd
index 669c4f5..80c8f86 100644
--- a/Src/Modules/curses.mdd
+++ b/Src/Modules/curses.mdd
@@ -2,7 +2,7 @@ name=zsh/curses
 link='if test "x$ac_cv_func_initscr" = xyes && test "x$zsh_cv_path_curses_header" != x; then echo dynamic; else echo no; fi'
 load=no
 
-autobins="zcurses"
+autofeatures="b:zcurses"
 
 objects="curses.o"