[asterisk-dev] Is 'make menuconfig' in dahdi-tools needed still?

[Tzafrir Cohen]

On Thu, Jan 20, 2011 at 10:15:17AM -0600, Tilghman Lesher wrote:
> On Wednesday 19 January 2011 19:08:25 Shaun Ruffell wrote:
> > I'm wondering if anyone uses "make menuconfig" when building dahdi-tools
> > anymore?
> > 
> > The following small-ish utilities are what is currently built in
> > dahdi-tools.
> > 
> > [*] fxotune
> > [ ] fxstest
> > [*] sethdlc
> > [*] dahdi_cfg
> > [ ] dahdi_diag
> > [*] dahdi_monitor
> > [*] dahdi_scan
> > [*] dahdi_speed
> > [*] dahdi_test
> > [*] dahdi_tool
> > 
> > On my test system, it takes longer to build menuselect/menuselect than
> > it does to build the utilities.
> > 
> > If you do not want menuselect to dissapear from dahdi-tools please speak
> > up.
> 
> 1) I think we should disable all but "dahdi_cfg" in the default install.
> The other tools are only needed in some very narrow circumstances.

Wasn't there already such a round of filtering with currrent defaults as
its output?

> 
> 2) I'd additionally like to see menuselect implemented for the kernel
> drivers, as there are flags in include/dahdi/dahdi_config.h that you need to
> alter in order to turn those options on (CONFIG_DAHDI_NET, for one).

The data for Kconfig is there. Now, how do we use it?
:-(

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir