manual: minor tweaks

Overall, for package library dependencies, +select+ should be

preferred.

Note that such dependencies will make sure that the dependency option

Note that such dependencies will ensure that the dependency option

is also enabled, but not necessarily built before your package. To do

so, the dependency also needs to be expressed in the +.mk+ file of the

package.

Further formating details: see xref:writing-rules-config-in[the

Further formatting details: see xref:writing-rules-config-in[the

writing rules].

The +.mk+ file

* *Makefiles for generic packages* (not using autotools or CMake):

  These are based on an infrastructure similar to the one used for

  autotools-based packages, but requires a little more work from the

  autotools-based packages, but require a little more work from the

  developer. They specify what should be done for the configuration,

  compilation, installation and cleanup of the package. This

  infrastructure must be used for all packages that do not use the

Many packages that support internationalization use the gettext

library. Dependencies for this library are fairly complicated and

therefore, deserves some explanation.

therefore, deserve some explanation.

The 'uClibc' C library doesn't implement gettext functionality,

The 'uClibc' C library doesn't implement gettext functionality;

therefore with this C library, a separate gettext must be compiled. On

the other hand, the 'glibc' C library does integrate its own gettext,

and in this case, the separate gettext library should not be compiled,

and in this case the separate gettext library should not be compiled,

because it creates various kinds of build failures.

Additionally, some packages (such as +libglib2+) do require gettext

Package name, config entry name and makefile variable relationship

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In Buildroot, there are some relation between:

In Buildroot, there is some relationship between:

* the _package name_, which is the package directory name (and the

  name of the +*.mk+ file);

* the makefile variable prefix.

Thus, it is mandatory to keep consistency between all this stuff,

matching the following rules:

It is mandatory to maintain consistency between these elements,

using the following rules:

* the _make_ target name will be the _package name_ itself (e.g.:

  +foo-bar_boo+);

To achieve NFS-boot, enable _tar root filesystem_ in the _Filesystem

images_ menu.

After complete build, just run the following commands to setup the

After a complete build, just run the following commands to setup the

NFS-root directory:

-------------------

root of the Buildroot source tree. Move this file into the +configs/+

directory, and rename it +MYBOARD_defconfig+.

It is recommended to use as much as possible upstream versions of the

Linux kernel and bootloaders, and to use as much as possible default

kernel and bootloader configurations. If they are incorrect for your

platform, we encourage you to send fixes to the corresponding upstream

It is recommended to use upstream versions of the Linux kernel and

bootloaders where possible, and also to use default kernel and bootloader

configurations if possible. If the defaults are incorrect for

your platform, we encourage you to send fixes to the corresponding upstream

projects.

However, in the mean time, you may want to store kernel or bootloader