manual: trivial fixes

* +LIBFOO_INSTALL_STAGING_OPT+ contains the make options

  used to install the package to the staging directory. By default, the

  value is +DESTDIR=$$(STAGING_DIR) install+, which is

  value is +DESTDIR=$(STAGING_DIR) install+, which is

  correct for most autotools packages. It is still possible to override

  it.

* +LIBFOO_INSTALL_TARGET_OPT+ contains the make options

  used to install the package to the target directory. By default, the

  value is +DESTDIR=$$(TARGET_DIR) install+. The default

  value is +DESTDIR=$(TARGET_DIR) install+. The default

  value is correct for most autotools packages, but it is still possible

  to override it if needed.

* +LIBFOO_INSTALL_STAGING_OPT+ contains the make options used to

  install the package to the staging directory. By default, the value

  is +DESTDIR=$$(STAGING_DIR) install+, which is correct for most

  is +DESTDIR=$(STAGING_DIR) install+, which is correct for most

  CMake packages. It is still possible to override it.

* +LIBFOO_INSTALL_TARGET_OPT+ contains the make options used to

  install the package to the target directory. By default, the value

  is +DESTDIR=$$(TARGET_DIR) install+. The default value is correct

  is +DESTDIR=$(TARGET_DIR) install+. The default value is correct

  for most CMake packages, but it is still possible to override it if

  needed.

according to the compilation process required by the package.

If you package software that might be useful for other people, don't

forget to send a patch to Buildroot developers!

forget to send a patch to the Buildroot mailing list!

your software, for example +libfoo+.

Some packages have been grouped by topic in a sub-directory:

+multimedia+, +java+, +x11r7+, and +games+. If your package fits in

+multimedia+, +x11r7+, +efl+ and +matchbox+. If your package fits in

one of these categories, then create your package directory in these.

  Examples: +

    +LIBFOO_SITE=http://www.libfoosoftware.org/libfoo+ +

    +LIBFOO_SITE=http://svn.xiph.org/trunk/Tremor/+ +

    +LIBFOO_SITE=git://github.com/kergoth/tslib.git+

    +LIBFOO_SITE=/opt/software/libfoo.tar.gz+

    +LIBFOO_SITE=git://github.com/kergoth/tslib.git+ +

    +LIBFOO_SITE=/opt/software/libfoo.tar.gz+ +

    +LIBFOO_SITE=$(TOPDIR)/../src/libfoo/+

* +LIBFOO_SITE_METHOD+ determines the method used to fetch or copy the

  name) that are required for the current target package to

  compile. These dependencies are guaranteed to be compiled and

  installed before the configuration of the current package starts. In

  a similar way, +HOST_LIBFOO_DEPENDENCIES+ lists the dependency for

  a similar way, +HOST_LIBFOO_DEPENDENCIES+ lists the dependencies for

  the current host package.

* +LIBFOO_INSTALL_STAGING+ can be set to +YES+ or +NO+ (default). If

Now, the variables that define what should be performed at the

different steps of the build process.

* +LIBFOO_CONFIGURE_CMDS+, used to list the actions to be performed to

  configure the package before its compilation

* +LIBFOO_CONFIGURE_CMDS+ lists the actions to be performed to

  configure the package before its compilation.

* +LIBFOO_BUILD_CMDS+, used to list the actions to be performed to

  compile the package

* +LIBFOO_BUILD_CMDS+ lists the actions to be performed to

  compile the package.

* +HOST_LIBFOO_INSTALL_CMDS+, used to list the actions to be performed

* +HOST_LIBFOO_INSTALL_CMDS+ lists the actions to be performed

  to install the package, when the package is a host package. The

  package must install its files to the directory given by

  +$(HOST_DIR)+. All files, including development files such as

  headers should be installed, since other packages might be compiled

  on top of this package.

* +LIBFOO_INSTALL_TARGET_CMDS+, used to list the actions to be

* +LIBFOO_INSTALL_TARGET_CMDS+ lists the actions to be

  performed to install the package to the target directory, when the

  package is a target package. The package must install its files to

  the directory given by +$(TARGET_DIR)+. Only the files required for

  to the target, if the +development files in target filesystem+

  option is selected.

* +LIBFOO_INSTALL_STAGING_CMDS+, used to list the actions to be

* +LIBFOO_INSTALL_STAGING_CMDS+ lists the actions to be

  performed to install the package to the staging directory, when the

  package is a target package. The package must install its files to

  the directory given by +$(STAGING_DIR)+. All development files

  should be installed, since they might be needed to compile other

  packages.

* +LIBFOO_CLEAN_CMDS+, used to list the actions to perform to clean up

* +LIBFOO_CLEAN_CMDS+, lists the actions to perform to clean up

  the build directory of the package.

* +LIBFOO_UNINSTALL_TARGET_CMDS+, used to list the actions to

* +LIBFOO_UNINSTALL_TARGET_CMDS+ lists the actions to

  uninstall the package from the target directory +$(TARGET_DIR)+

* +LIBFOO_UNINSTALL_STAGING_CMDS+, used to list the actions to

* +LIBFOO_UNINSTALL_STAGING_CMDS+ lists the actions to

  uninstall the package from the staging directory +$(STAGING_DIR)+.

* +LIBFOO_INSTALL_INIT_SYSV+ and +LIBFOO_INSTALL_INIT_SYSTEMD+, used

  to install init scripts either for the systemV-like init systems

* +LIBFOO_INSTALL_INIT_SYSV+ and +LIBFOO_INSTALL_INIT_SYSTEMD+ list the

  actions to install init scripts either for the systemV-like init systems

  (busybox, sysvinit, etc.) or for the systemd units. These commands

  will be run only when the relevant init system is installed (i.e. if

  systemd is selected as the init system in the configuration, only

they are provided by the generic infrastructure, they are documented

here. The exception is +LIBFOO_POST_PATCH_HOOKS+.  Patching the

package and producing legal info are not user definable, so

+LIBFOO_POST_PATCH_HOOKS+ and +LIBFOO_POST_LEGAL_INFO_HOOKS+ will be

userful for generic packages.

+LIBFOO_POST_PATCH_HOOKS+ and +LIBFOO_POST_LEGAL_INFO_HOOKS+ are

useful for generic packages.

The following hook points are available: