[En-Nut-Discussion] Trouble with nutconf and 'nut' subdirectory + make question
harald.kipp at egnite.de
Thu Sep 8 18:04:37 CEST 2005
At 12:17 01.09.2005 +0200, you wrote:
>FYI: I just lost a lot of time because nowhere it is written that there
>must be a symlink like
>ln -s ethernut-3.9.8 nut
>for 'nutconf' to work.
I'm sorry for this waste of your time. I recently ran into
similar trouble, though I had been able to make it work
without setting a symlink. One problem might be caused by
an existing ~/.NutConf initialization file. In case of
trouble after upgrading Nut/OS, I'd suggest to remove
this file before starting nutconf.
Another problem is, that the Linux archive doesn't contain
the intended directory structure, which is
ethernut-x.y.z (Install directory)
nut (Source tree)
nutbld (Build tree, created by nutconf)
nutapp (Application tree, also by nutconf)
Instead, source and install directory are the same. I have
no idea how to fix this without moving the complete CVS
tree one directory level down. Another option would be,
to give up this structure and change the Windows Installer.
(Sigh, then I'd have to change all my nicely set up test
directories and related scripts.)
As a temporary fix I manually created a new source package,
which reflects the intended directory structure. After
unpacking and installing this archive with
$ cd ethernut-3.9.8-2
$ rm ~/.NutConf
# make install
you should be able to run nutconf (from the install dir)
and most settings should be usable with their default values.
Except Platform and environment path. Usually the latter can
be left empty on Linux anyway, as the tools will be moved to
/usr/local/bin/ during 'make install'.
The new, hacked package is available at
More information about the En-Nut-Discussion