Commit ad219f53 authored by Alessandro Rubini's avatar Alessandro Rubini

doc: documented Kconfig use

Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
parent f8bc3bcb
...@@ -343,17 +343,37 @@ First you have to compile the tools provided with WRPC software which are used ...@@ -343,17 +343,37 @@ First you have to compile the tools provided with WRPC software which are used
later during the software compilation: later during the software compilation:
@example @example
$ cd tools $ make -C tools
$ make @end example
$ cd ..
Now you have everything that is needed to build the software for WRPC,
but you need to make a few configuration choices. The package is using
@i{Kconfig} as a configuration engine, so you may run one of the
following commnads (the first is text-mode, the second uses a KDE GUI
and the third uses a Gnome GUI):
@example
$ make menuconfig
$ make xconfig
$ make gconfig
@end example @end example
Now you have everything that is needed to build the software for WRPC. Before Other @i{Kconfig} target applies, like @code{config}, @code{oldconfig}
compilation the decision can be made whether to turn on or not the software and so on. A few default known-good configurations are found in
support for Etherbone core that is integrated inside WRPC gateware for SPEC @file{./configs} and you choose them by @i{make}ing them by name
board. By default it is disabled but can be turned on by setting the like this:
@i{CONFIG_ETHERBONE} variable to @i{y} inside the Makefile. The compilation is made by
a simple command without any additional parameters: @example
$ make spec_defconfig
@end example
The most important configuration choice at this point in time is
whether to enable Etherbone or not. It is disabled by default in
@code{spec_defconfig} and enabled by default in
@code{etherbone_defconfig}.
After the package is configured, just run @code{make} without
parameters to build your binary file:
@example @example
$ make $ make
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment