From 8146fc687d865709b61374ebb9509942cc2de0f9 Mon Sep 17 00:00:00 2001 From: Bernhard Reutner-Fischer Date: Fri, 19 Jan 2007 12:35:26 +0000 Subject: - some minor corrections --- docs/buildroot.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'docs') diff --git a/docs/buildroot.html b/docs/buildroot.html index cec8b6ae5..f99339e90 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -395,7 +395,7 @@ mips-linux-gcc -o foo foo.c

If you want to use the generated toolchain for other purposes, you can configure Buildroot to generate it elsewhere using the - option of the configuration tool : Build options -> + option of the configuration tool : Build options -> Toolchain and header file location, which defaults to $(BUILD_DIR)/staging_dir/.

@@ -434,7 +434,9 @@ config BR2_PACKAGE_FOO bool "foo" default n help - This is a comment that explains what foo is. + This is a comment that explains what foo is. + + http://foosoftware.org/foo/

Of course, you can add other options to configure particular @@ -607,7 +609,7 @@ config BR2_PACKAGE_FOO if all package-sources are downloadable.

Lines 44-46 define a simple target to clean the software build - by calling the Makefiles with the appropriate option.
+ by calling the Makefiles with the appropriate option. The clean target should run make clean on $(BUILD_DIR)/package-version and MUST uninstall all files of the package from $(STAGING_DIR) and from $(TARGET_DIR).

@@ -650,12 +652,10 @@ config BR2_PACKAGE_FOO - - Valid HTML - + Valid HTML -- cgit v1.2.3