X-Git-Url: http://git.rohieb.name/openwrt.git/blobdiff_plain/796a9d1091884a07817e5c140d0ff6a0b8c76235..8270d590f1e3dbcb49591a551a4d9bda4b2d84a3:/docs/build.tex diff --git a/docs/build.tex b/docs/build.tex index c85eed80e..6e1539acf 100644 --- a/docs/build.tex +++ b/docs/build.tex @@ -41,11 +41,10 @@ So let's take a look at OpenWrt and see how this all works. \subsubsection{Download OpenWrt} -This article refers to the "Kamikaze" branch of OpenWrt, which can be downloaded via -subversion using the following command: +OpenWrt can be downloaded via subversion using the following command: \begin{Verbatim} -$ svn checkout https://svn.openwrt.org/openwrt/trunk kamikaze +$ svn checkout svn://svn.openwrt.org/openwrt/trunk openwrt-trunk \end{Verbatim} Additionally, there is a trac interface on \href{https://dev.openwrt.org/}{https://dev.openwrt.org/} @@ -88,7 +87,7 @@ $ ./scripts/feeds update Those packages can be used to extend the functionality of the build system and need to be symlinked into the main trunk. Once you do that, the packages will show up in the menu for -configuration. From kamikaze you would do something like this: +configuration. You would do something like this: \begin{Verbatim} $ ./scripts/feeds search nmap @@ -182,7 +181,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} @@ -293,7 +292,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} \\