[En-Nut-Discussion] NutOS configurator

[Henrik Maier]

kconfig is console based, isn't it?

Despite being just a configurator, I believe there is another aspect of
nutconf:

It visually presents Nut/OS' structure, modularity and capabilities very
well. A user can quickly browse through the configuration tree and see what
capabilities are available with a few mouse clicks. Good in particular
because a lot of these features and configuration options are not documented
anywhere else.

It is also very nice to demonstrate the powerful architecture and
capabilities of Nut/OS to a potential new user in a visually pleasing way.
 
I doubt that a console based tool would have the same impact on a
potentially new user in order to evaluate whether to go with Nut/OS or
another solution.

Henrik

> -----Original Message-----
> From: Ole Reinhardt [mailto:ole.reinhardt at embedded-it.de]
> Sent: Monday, 15 October 2007 6:33 AM
> To: Ethernut User Chat (English)
> Subject: Re: [En-Nut-Discussion] NutOS configurator
> 
> Hi,
> 
> > I wasn't aware that either kconfig (or kbuild) used on Linux kernel
> > build or KDE's KConfig has native versions running on Windows? Which one
> > were you talking about, or perhaps yet another? I tried to google for
> > kconfig but didn't find any good sources, perhaps you can share URL?
> 
> Indeed it does not have a "native" version, but the code shoule be
> 
> a.) portable
> b.) run well in cygwin.
> 
> Cygwin is needed for the gcc / make environment anyway. Kconfig is a
> modified version of dialog, which itself depends on ncurses. But ncurses
> should be available for windows as well.