OpenIPC
/
wiki
mirror of https://github.com/OpenIPC/wiki.git
1
0
Fork 0
Code Activity

Adjust commands to run from firmware root

pull/86/head
Paul Philippov 2023-04-02 12:18:32 -04:00 committed by GitHub
parent 0920f5bd76
commit 08c57b5c1d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
en/building.md
View File

@ -142,23 +142,22 @@ Making changes and rebuilding a package
Once you start tinkering with the packages you'll realize you need a way to Once you start tinkering with the packages you'll realize you need a way to
rebuld only one particular package, without rebuilding the whole project. rebuld only one particular package, without rebuilding the whole project.
Is it even possible? Fortunately, yes. All you have to do after making changes Is it even possible? Fortunately, yes. All you have to do after making changes
to the package configs is to step into the `output/` directory and run a couple to the package configs is to run a couple of commands:
of commands:
``` ```
make <package>-dirclean make br-<package>-dirclean
make <package>-rebuild make br-<package>-rebuild
``` ```
where _\<package>_ is the name of the package you want to recompile. Although, where _\<package>_ is the name of the package you want to recompile. Although,
as Buildroot manual states, as Buildroot manual states,
> While `<package>-rebuild` implies `<package>-reinstall` and `<package>-reconfigure` > While `br-<package>-rebuild` implies `br-<package>-reinstall` and `br-<package>-reconfigure`
implies `<package>-rebuild`, these targets as well as `<package>` only act on implies `br-<package>-rebuild`, these targets as well as `<package>` only act on
the said package, and do not trigger re-creating the root filesystem image. the said package, and do not trigger re-creating the root filesystem image.
If re-creating the root filesystem in necessary, one should in addition run If re-creating the root filesystem in necessary, one should in addition run
`make` or `make all`. `make` or `make all`.
Run `make linux-rebuild all` to rebuild Linux kernel image, Run `make br-linux-rebuild all` to rebuild Linux kernel image,
`make busybox-rebuild all` to rebuild busybox and pack it into a rootfs image. `make br-busybox-rebuild all` to rebuild busybox and pack it into a rootfs image.
Making changes to Buildroot packages Making changes to Buildroot packages
------------------------------------ ------------------------------------
@ -186,10 +185,10 @@ Compilation process has also built a toolchain suitable for compiling packages
for your version of firmware. The toolchain is located in `output/host` for your version of firmware. The toolchain is located in `output/host`
directory. directory.
To customize your firmware, add or remove a package, go to `output/` directory To customize your firmware, add or remove a package run `make br-menuconfig`.
and run `make menuconfig`. That will load buildroot configuration menu where That will load buildroot configuration menu where you can make changes following
you can make changes following [The Buildroot user manual][5]. Make your [The Buildroot user manual][5]. Make your changes and save amended config on exit.
changes and save amended config on exit. Then run `make clean all`. Then run `make clean all`.
__Be aware that building firmware directly with buildroot will not rename __Be aware that building firmware directly with buildroot will not rename
resulting image files adding a soc suffix to them. You either can to it resulting image files adding a soc suffix to them. You either can to it