1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
|
misc/tools/README.txt
=====================
Contents:
o genromfs-0.5.2.tar.gz
o kconfig-frontends
- --program-prefix=
- kconfig-frontends-3.3.0-1-libintl.patch
- kconfig-macos.patch
- kconfig-macos.patch
- kconfig-frontends for Windows
genromfs-0.5.2.tar.gz
=====================
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.
kconfig-frontends
=================
This is a snapshot of the kconfig-frontends version 3.12.0 tarball taken
from http://ymorin.is-a-geek.org/projects/kconfig-frontends.
General build instructions:
cd kconfig-frontends
./configure --enable-mconf
make
make install
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
make
make install
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
make
make install
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
make
make install
Or,
./configure --enable-mconf --disable-nconf --enable-gconf --disable-qconf
make
make install
In these case, you can start the graphical configurator in the nuttx/
directory with either:
make qconfig
or
make gconfig
--program-prefix=
-----------------
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.
kconfig-frontends-3.3.0-1-libintl.patch
---------------------------------------
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
cd kconfig-frontends-3.3.0-1
./configure --disable-gconf --disable-qconf
make
make install
See: http://ymorin.is-a-geek.org/hg/kconfig-frontends/file/tip/docs/known-issues.txt
Update: Version 3.6.0 (and above) will build on Cygwin with no patches:
http://ymorin.is-a-geek.org/download/kconfig-frontends/
kconfig-macos.patch
-------------------
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
make
make install
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
ldconfig tool.
2) Specify the LD_RUN_PATH environment when building the kconfig-frontends
tools like:
./configure --enable-mconf
LD_RUN_PATH=/usr/local/lib make
make install
I have also been told that some people see this error until they re-boot, then it
just goes away.
gperf
-----
"I am getting an error when configuring the kconfig-frontends-3.12.0.0 package.
Using command
./configure --enable-mconf
"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:
http://uvc.de/posts/linux-kernel-configuration-tool-mconf-under-windows.html
[The remainder of the text in this section is for historical interest only]
From http://tech.groups.yahoo.com/group/nuttx/message/2900:
"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
--disable-shared
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
osmocon
=======
This is the osmocon utility extracted from the Osmocom-BB git on 2013-5-14. It
has been modified to build standalone outside of the Osmocom-BB environment.
Osmocom-BB developers will have no use for this tool since it is available in
the Osmocom-BB repository. However, it is handle for OS developers who will
not be building the entire phone application.
See the Osmocom-BB Getting Started page for instructions for the use of this
tool. NOTE: This tool has a GPL license. See osmocom/COPYING.
|
