Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
lede-mikrotik
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Johannes Rudolph
lede-mikrotik
Commits
4ba4822f
Commit
4ba4822f
authored
17 years ago
by
Felix Fietkau
Browse files
Options
Downloads
Patches
Plain Diff
update build directory paths
SVN-Revision: 10000
parent
7e712d11
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/build.tex
+10
-10
10 additions, 10 deletions
docs/build.tex
with
10 additions
and
10 deletions
docs/build.tex
+
10
−
10
View file @
4ba4822f
...
@@ -65,16 +65,16 @@ There are four key directories in the base:
...
@@ -65,16 +65,16 @@ There are four key directories in the base:
\texttt
{
tools
}
and
\texttt
{
toolchain
}
refer to common tools which will be
\texttt
{
tools
}
and
\texttt
{
toolchain
}
refer to common tools which will be
used to build the firmware image, the compiler, and the C library.
used to build the firmware image, the compiler, and the C library.
The result of this is three new directories,
\texttt
{
tool
\_
build
}
, which is a temporary
The result of this is three new directories,
\texttt
{
build
\_
dir
/
host
}
, which is a temporary
directory for building the target independent tools,
\texttt
{
toolchain
\_
build
\_
\textit
{
<arch>
}}
directory for building the target independent tools,
\texttt
{
build
\_
dir
/
toolchain
-
\textit
{
<arch>
}
*
}
which is used for building the toolchain for a specific architecture, and
which is used for building the toolchain for a specific architecture, and
\texttt
{
staging
\_
dir
\_
\textit
{
<arch>
}}
where the resulting toolchain is installed.
\texttt
{
staging
\_
dir
/
toolchain
-
\textit
{
<arch>
}
*
}
where the resulting toolchain is installed.
You will not need to do anything with the toolchain directory unless you intend to
You will not need to do anything with the toolchain directory unless you intend to
add a new version of one of the components above.
add a new version of one of the components above.
\begin
{
itemize
}
\begin
{
itemize
}
\item
\texttt
{
tool
\_
build
}
\item
\texttt
{
build
\_
dir
/
host
}
\item
\texttt
{
toolchain
\_
build
\_
\textit
{
<arch>
}}
\item
\texttt
{
build
\_
dir
/
toolchain
-
\textit
{
<arch>
}
*
}
\end
{
itemize
}
\end
{
itemize
}
\texttt
{
package
}
is for exactly that
--
packages. In an OpenWrt firmware, almost everything
\texttt
{
package
}
is for exactly that
--
packages. In an OpenWrt firmware, almost everything
...
@@ -108,12 +108,12 @@ directory which is broken down by platform \textit{<arch>} and contains the patc
...
@@ -108,12 +108,12 @@ directory which is broken down by platform \textit{<arch>} and contains the patc
kernel, profile config, for a particular platform. There's also the "
\texttt
{
target
/
image
}
" directory
kernel, profile config, for a particular platform. There's also the "
\texttt
{
target
/
image
}
" directory
which describes how to package a firmware for a specific platform.
which describes how to package a firmware for a specific platform.
Both the target and package steps will use the directory "
\texttt
{
build
\_\textit
{
<arch>
}}
"
Both the target and package steps will use the directory "
\texttt
{
build
\_
dir
/
\textit
{
<arch>
}}
"
as a temporary directory for compiling. Additionally, anything downloaded by the toolchain,
as a temporary directory for compiling. Additionally, anything downloaded by the toolchain,
target or package steps will be placed in the "
\texttt
{
dl
}
" directory.
target or package steps will be placed in the "
\texttt
{
dl
}
" directory.
\begin
{
itemize
}
\begin
{
itemize
}
\item
\texttt
{
build
\_\textit
{
<arch>
}}
\item
\texttt
{
build
\_
dir
/
\textit
{
<arch>
}}
\item
\texttt
{
dl
}
\item
\texttt
{
dl
}
\end
{
itemize
}
\end
{
itemize
}
...
@@ -171,7 +171,7 @@ of noise caused by the compile output. To see the full output, run the command
...
@@ -171,7 +171,7 @@ of noise caused by the compile output. To see the full output, run the command
"
\texttt
{
make V
=
99
}
".
"
\texttt
{
make V
=
99
}
".
During the build process, buildroot will download all sources to the "
\texttt
{
dl
}
"
During the build process, buildroot will download all sources to the "
\texttt
{
dl
}
"
directory and will start patching and compiling them in the "
\texttt
{
build
\_\textit
{
<arch>
}}
"
directory and will start patching and compiling them in the "
\texttt
{
build
\_
dir
/
\textit
{
<arch>
}}
"
directory. When finished, the resulting firmware will be in the "
\texttt
{
bin
}
" directory
directory. When finished, the resulting firmware will be in the "
\texttt
{
bin
}
" directory
and packages will be in the "
\texttt
{
bin
/
packages
}
" directory.
and packages will be in the "
\texttt
{
bin
/
packages
}
" directory.
...
@@ -465,10 +465,10 @@ run one of the following:
...
@@ -465,10 +465,10 @@ run one of the following:
\item
\texttt
{
make package/
\textit
{
<name>
}
/install V=99
}
\item
\texttt
{
make package/
\textit
{
<name>
}
/install V=99
}
\end{itemize}
\end{itemize}
Another nice trick is that if the source directory under
\texttt
{
build
\_\textit
{
<arch>
}}
Another nice trick is that if the source directory under
\texttt
{
build
\_
dir/
\textit
{
<arch>
}}
is newer than the package directory, it won't clobber it by unpacking the sources again.
is newer than the package directory, it won't clobber it by unpacking the sources again.
If you were working on a patch you could simply edit the sources under the
If you were working on a patch you could simply edit the sources under the
\texttt
{
build
\_\textit
{
<arch>
}
/
\textit
{
<source>
}}
directory and run the install command above,
\texttt
{
build
\_
dir/
\textit
{
<arch>
}
/
\textit
{
<source>
}}
directory and run the install command above,
when satisfied, copy the patched sources elsewhere and diff them with the unpatched
when satisfied, copy the patched sources elsewhere and diff them with the unpatched
sources. A warning though - if you go modify anything under
\texttt
{
package/
\textit
{
<name>
}}
sources. A warning though - if you go modify anything under
\texttt
{
package/
\textit
{
<name>
}}
it will remove the old sources and unpack a fresh copy.
it will remove the old sources and unpack a fresh copy.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment