- General Build Instructions
- Graphical Configuration Tools
- kconfig-mconf Path Issues
- kconfig-frontends for Windows
This is a snapshot of the genromfs tarball taken from
http://sourceforge.net/projects/romfs/. This snapshot is provided to
assure that a working version of genromfs is always available for NuttX.
This tool is also include in the buildroot and can be built automatically
from the buildroot.
General Build Instructions
This is a snapshot of the kconfig-frontends version 3.12.0 tarball taken
General build instructions:
It is a good idea to add '--enable-mconf' on the 'configure' command line.
The kconfig-frontends make will generate many programs, but the NuttX
build system only needs the 'kconfig-conf' and 'kconfig-mconf' programs.
If the requirements for 'kconfig-mconf' are not supported by your system,
the kconfig-frontends configuration system will not build it. Adding the
option --enable-mconf assures you that 'kconfig-mconf' will be built or
if it is not built, it will tell you why it was not built.
To suppress the 'nconf' and the graphical front-ends which are not used by
NuttX, you can add:
./configure --enable-mconf --disable-nconf --disable-gconf --disable-qconf
To suppress the graphical interfaces, use static libraries, and disable
creation of other utilities:
./configure --disable-shared --enable-static --enable-mconf --disable-nconf --disable-gconf --disable-qconf --disable-nconf --disable-utils
The default installation location for the tools is /usr/local/bin. You
may require root privileges to 'make install'.
Graphical Configuration Tools
If you have an environment that suppots the Qt or GTK graphical systems
(probably KDE or gnome, respectively), then you can also build the
graphical kconfig-frontends, kconfig-qconf and kconfig-gconf:
./configure --enable-mconf --disable-nconf --disable-gconf --enable-qconf
./configure --enable-mconf --disable-nconf --enable-gconf --disable-qconf
In these case, you can start the graphical configurator in the nuttx/
directory with either:
Beginning somwhere between version 3.3.0 and 3.6.0, the prefix was added
to the kconfig-frontends tools. The default prefix is kconfig-. So,
after 3.3.0, conf becomes kconfig-conf, mconf becomes kconfig-mconf, etc.
All of the NuttX documentation, Makefiles, scripts have been updated to
used this default prefix.
This introduces an incompatibility with the 3.3.0 version. In the 3.6.0
timeframe, the configure argument --program-prefix= was added to
eliminated the kconfig- prefix. This, however, caused problems when we
got to the 3.7.0 version which generates a binary called kconfig-diff
(installed at /usr/local/bin). Without the prefix, may conflict with
the standard diff utility (at /bin), depending upon how your PATH
variable is configured. Because of this, we decided to "bite the bullet"
and use the standard prefix at 3.7.0 and later.
This problem could probably also be avoided using --disable-utils.
The above build instructions did not work for me under my Cygwin
installation with kconfig-frontends-3.3.0. This patch is a awful hack
but will successfully build 'kconfig-mconf' under Cygwin.
cat kconfig-frontends-3.3.0-1-libintl.patch | patch -p0
./configure --disable-gconf --disable-qconf
Update: Version 3.6.0 (and above) will build on Cygwin with no patches:
This is a patch to make the kconfig-frontends-3.3.0 build on Mac OS X.
To build the conf and mconf frontends, use the following commands:
./configure --disable-shared --enable-static --disable-gconf --disable-qconf --disable-nconf --disable-utils
kconfig-mconf Path Issues
Some people have experienced this problem after successfully building and installing
the kconfig-frontends tools:
kconfig-mconf: error while loading shared libraries: libkconfig-parser-3.8.0.so: cannot open shared object file: No such file or directory
make: *** [menuconfig] Error 127
There two known solutions to this:
1) Add the directory where the kconfig-frontends libraries were installed
to the file /etc//ld.so.conf (probably /usr/local/lib), then run the
2) Specify the LD_RUN_PATH environment when building the kconfig-frontends
3) Build the kconfig-frontends tools using only static libraries:
./configure --enable-mconf --disable-shared --enable-static
I have also been told that some people see this error until they re-boot, then it
just goes away. I would try that before anything else.
"I am getting an error when configuring the kconfig-frontends-184.108.40.206 package.
"It says it 'configure: error: can not find gperf'"
If you see this, make sure that the gperf package is installed.
kconfig-frontends for Windows
Recent versions of NuttX support building NuttX from a native Windows
console window (see "Native Windows Build" below). But kconfig-frontends
is a Linux tool. At one time this was a problem for Windows users, but
now there is a specially modified version of the kconfig-frontends tools
that can be used:
[The remainder of the text in this section is for historical interest only]
"The build was quite simple:
I used mingw installer and I had to install two packages that the
automated mingw setup does not bring by default:
* mingw-get update
* mingw-get install mingw32-pdcurses mingw32-libpdcurses
* mingw-get install msys-regex msys-libregex
(grep the output of mingw-get list if I got the names wrong)
Then I had to change some things in mconf code, it was quite simple to
understand the make errors.
* The first of them is to disable any use of uname() in symbol.c and
replace the uname output by a constant string value (I used MINGW32-MSYS),
* The second one is related to the second parameter to mkdir() that has
to disappear for windows (we don't care about folder rights) in confdata.c;
* And the last one of them involves #undef bool in dialog.h before including
curses.h (CURSES_LOC), around line 30.
I wrapped all of my changes in #if(n)def __MINGW32__, but that is not
sufficient to make that work everywhere, I think.
So mconf itself has some portability issues that shall be managed in a
cleaner way, what I did was just hacks, I don't think they are
acceptable by mconf upstream maintainers.
Here is the magic incantation to get the whole thing working. It seems
that the configure script is not so good and does not bring the required
bits to link libregex.
CFLAGS="-I/mingw/include -I/usr/include" LDFLAGS="-Bstatic -L/mingw/lib
-L/usr/lib -lregex" ./configure --enable-frontends=mconf --enable-static
So the message I want to pass is that native "make menuconfig" in
windows IS POSSIBLE, I have done it in a few minutes."
"Oops, forgot something, I had to bring a gperf binary from the gnuwin32 project."
- Sebastien Lorquet
As of 2014-3-7, the kconfig-frontends tools have been included in the
buildroot tool set. This means that in one package you can build GCC tools
that are especially tuned for NuttX and all of the support tools that you
need ROMFS, configuration, and NXFLAT.
A Linux FUSE implmentation that enables native mounting of NuttX filesystems
in Linux. Currently supports SmartFS and NXFFS (within the limitations of
the NXFFS architecture). See the nxfuse/README.txt file for further information.