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
7230c235
Commit
7230c235
authored
19 years ago
by
Felix Fietkau
Browse files
Options
Downloads
Patches
Plain Diff
remove deprecated customization method from buildroot documentation
SVN-Revision: 2218
parent
3da601a8
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
openwrt/docs/buildroot-documentation.html
+7
-19
7 additions, 19 deletions
openwrt/docs/buildroot-documentation.html
with
7 additions
and
19 deletions
openwrt/docs/buildroot-documentation.html
+
7
−
19
View file @
7230c235
...
...
@@ -156,25 +156,13 @@
<h2><a
name=
"custom_targetfs"
id=
"custom_targetfs"
></a>
Customizing the
target filesystem
</h2>
<p>
There are two ways to customize the resulting target filesystem:
</p>
<ul>
<li>
Customize the target filesystem directly, and rebuild the image. The
target filesystem is available under
<code>
build_ARCH/root/
</code>
where
<code>
ARCH
</code>
is the chosen target architecture, usually mipsel.
You can simply make your changes here, and run make target_install afterwards,
which will rebuild the target filesystem image. This method allows to do
everything on the target filesystem, but if you decide to rebuild your toolchain,
tools or packages, these changes will be lost.
</li>
<li>
Customize the target filesystem skeleton, available under
<code>
package/base-files/default/
</code>
. You can customize
configuration files or other stuff here. However, the full file hierarchy
is not yet present, because it's created during the compilation process.
So you can't do everything on this target filesystem skeleton, but
changes to it remains even when you completely rebuild the cross-compilation
toolchain and the tools.
<br
/>
</ul>
<li>
You can customize the target filesystem skeleton, available under
<code>
package/base-files/default/
</code>
. You can change
configuration files or other stuff here. However, the full file hierarchy
is not yet present, because it's created during the compilation process.
So you can't do everything on this target filesystem skeleton, but
changes to it remains even when you completely rebuild the cross-compilation
toolchain and the tools.
<br
/>
<h2><a
name=
"custom_busybox"
id=
"custom_busybox"
></a>
Customizing the
Busybox configuration
</h2>
...
...
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