embedded wireless GmbH MORIN01 Manual Do Utilizador
MORIN Module. B2B-Module.
2
Documentation
the firmware image file.
▪
pressing m sets the <M> package label This package will be compiled, but not
included in the firmware image file. (E.g. to be installed with
opkg
after
flashing
the firmware image file to the device.)
▪
pressing n sets the < > excluded label The source code will not be processed.
When you save your configuration, the file <buildroot dir>/.config will be created
according to your configuration.
according to your configuration.
Explanations
It has been the intention from the beginning, with the development of menuconfig, to
create a simple, yet powerful, environment for the configuration of individual OpenWrt
builds. menuconfig is more or less self-explanatory, and even the most specialized
configuration requirements can be met by using it. Depending on the the particular
target platform, package requirements and kernel module needs, the standard
configuration process will include modifying:
create a simple, yet powerful, environment for the configuration of individual OpenWrt
builds. menuconfig is more or less self-explanatory, and even the most specialized
configuration requirements can be met by using it. Depending on the the particular
target platform, package requirements and kernel module needs, the standard
configuration process will include modifying:
1
Target system
2
Package selection
3
Build system settings
4
Kernel modules
Target system is selected from the extensive list of supported platforms, with the
numerous target profiles – ranging from specific devices to generic profiles, all
depending on the particular device at hand. Package selection has the option of either
'selecting all package', which might be un-practical in certain situation, or relying on the
default set of packages will be adequate or make an individual selection. It is here
needed to mention that some package combinations might break the build process, so
it can take some experimentation before the expected result is reached. Added to this,
the OpenWrt developers are themselves only maintaining a smaller set of packages –
which includes all default packages – but, the feeds-script makes it very simple to
handle a locally maintained set of packages and integrate them in the build-process.
The final step before the process of compiling the intended image(s) is to exit
menuconfig – this also includes the option to save a specific configuration or load an
already existing, and pre-configured, version.
Exit the TUI, and choose to save your settings.
numerous target profiles – ranging from specific devices to generic profiles, all
depending on the particular device at hand. Package selection has the option of either
'selecting all package', which might be un-practical in certain situation, or relying on the
default set of packages will be adequate or make an individual selection. It is here
needed to mention that some package combinations might break the build process, so
it can take some experimentation before the expected result is reached. Added to this,
the OpenWrt developers are themselves only maintaining a smaller set of packages –
which includes all default packages – but, the feeds-script makes it very simple to
handle a locally maintained set of packages and integrate them in the build-process.
The final step before the process of compiling the intended image(s) is to exit
menuconfig – this also includes the option to save a specific configuration or load an
already existing, and pre-configured, version.
Exit the TUI, and choose to save your settings.
Kernel configuration (optional)
Note that make kernel_menuconfig modifies the Kernel configuration templates of