diff options
| -rw-r--r-- | docs/buildroot.html | 18 |
1 files changed, 9 insertions, 9 deletions
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 <p>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 : <code>Build options -> + option of the configuration tool : <code>Build options -> Toolchain and header file location</code>, which defaults to <code>$(BUILD_DIR)/staging_dir/</code>.</p> @@ -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/ </pre> <p>Of course, you can add other options to configure particular @@ -607,7 +609,7 @@ config BR2_PACKAGE_FOO if all package-sources are downloadable.</p> <p>Lines <a href="#line44">44-46</a> define a simple target to clean the software build - by calling the <i>Makefiles</i> with the appropriate option.<br> + by calling the <i>Makefiles</i> with the appropriate option. The <code>clean</code> target should run <code>make clean</code> on $(BUILD_DIR)/package-version and MUST uninstall all files of the package from $(STAGING_DIR) and from $(TARGET_DIR).</p> @@ -650,12 +652,10 @@ config BR2_PACKAGE_FOO </div> <!-- --> - <td> - <a href="http://validator.w3.org/check?uri=referer"><img - border="0" height="31" width="88" - src="images/valid-html401.png" - alt="Valid HTML"></a> - </td> + <a href="http://validator.w3.org/check?uri=referer"><img + border="0" height="31" width="88" + src="images/valid-html401.png" + alt="Valid HTML"></img></a> <!-- --> |