X-Git-Url: https://git.rohieb.name/openwrt.git/blobdiff_plain/d6594675f08205e2086c383371c9251c51bd3c5a..e22bf04e2c7a06c4d3b5e72b061b98387ebb1ed8:/docs/build.tex diff --git a/docs/build.tex b/docs/build.tex index 9dfce5937..6828a2318 100644 --- a/docs/build.tex +++ b/docs/build.tex @@ -45,7 +45,7 @@ This article refers to the "Kamikaze" branch of OpenWrt, which can be downloaded subversion using the following command: \begin{Verbatim} -$ svn checkout https://svn.openwrt.org/openwrt/trunk kamikaze +$ svn checkout svn://svn.openwrt.org/openwrt/trunk kamikaze \end{Verbatim} Additionally, there is a trac interface on \href{https://dev.openwrt.org/}{https://dev.openwrt.org/} @@ -182,7 +182,7 @@ and packages will be in the "\texttt{bin/packages}" directory. One of the things that we've attempted to do with OpenWrt's template system is make it incredibly easy to port software to OpenWrt. If you look at a typical package directory -in OpenWrt you'll find two things: +in OpenWrt you'll find several things: \begin{itemize} \item \texttt{package/\textit{}/Makefile} @@ -204,7 +204,6 @@ simplifies the entire ordeal. Here for example, is \texttt{package/bridge/Makefile}: \begin{Verbatim}[frame=single,numbers=left] -# $Id: Makefile 5624 2006-11-23 00:29:07Z nbd $ include $(TOPDIR)/rules.mk @@ -294,7 +293,7 @@ directly as the Nth argument to \texttt{BuildPackage}. \begin{itemize} \item \texttt{SECTION} \\ - The type of package (currently unused) + The section of package (currently unused) \item \texttt{CATEGORY} \\ Which menu it appears in menuconfig: Network, Sound, Utilities, Multimedia ... \item \texttt{TITLE} \\ @@ -307,6 +306,9 @@ directly as the Nth argument to \texttt{BuildPackage}. Which packages must be built/installed before this package. To reference a dependency defined in the same Makefile, use \textit{}. If defined as an external package, use \textit{+}. For a kernel version dependency use: \textit{@LINUX\_2\_} + \item \texttt{BUILDONLY} (optional) \\ + Set this option to 1 if you do NOT want your package to appear in menuconfig. + This is useful for packages which are only used as build dependencies. \end{itemize} \textbf{\texttt{Package/\textit{}/conffiles} (optional):} \\ @@ -391,7 +393,6 @@ To do so, you can use the following template, which basically sets to nothing th Compile templates. \begin{Verbatim}[frame=single,numbers=left] -# $Id: $ include $(TOPDIR)/rules.mk @@ -448,7 +449,6 @@ For external kernel modules, you can add them to the build system just like if t Here for instance the Makefile for the I2C subsytem kernel modules : \begin{Verbatim}[frame=single,numbers=left] -# $Id $ I2CMENU:=I2C Bus @@ -547,7 +547,7 @@ The script \texttt{./scripts/env} is used to manage these environments, it uses The command \begin{Verbatim} - \texttt{./scripts/env help} + ./scripts/env help \end{Verbatim} produces a short help text with a list of commands.