5e84b8b73c
The new skeleton of the manual as it has been thought:
1. About Buildroot:
Presentation of Buildroot
2. Starting up:
Everything to quickly and easily start working with Buildroot
3. Working with Buildroot
Basics to make your work fitting your needs
4. Troubleshooting
5. Going further in Buildroot's innards
Explaination of how buildroot is organised, how it works, etc
6. Developer Guidelines
7. Getting involved
8. Contibuting to Buildroot
9. Legal notice
10. Appendix
It is easy to distinguish two parts in this plan:
- Sections 1 to 4 mainly address people starting with Buildroot
- Sections 5 to 10 are more focused on how to develop Buildroot itself
Most of the existing sections have just been moved in the hierarchy,
few were split and dispatch in, what i think was the relevant section,
and numerous others have been created.
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
25 lines
1002 B
Plaintext
25 lines
1002 B
Plaintext
// -*- mode:doc -*- ;
|
|
|
|
[[ccache]]
|
|
Using +ccache+ in Buildroot
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
http://ccache.samba.org[ccache] is a compiler cache. It stores the
|
|
object files resulting from each compilation process, and is able to
|
|
skip future compilation of the same source file (with same compiler
|
|
and same arguments) by using the pre-existing object files. When doing
|
|
almost identical builds from scratch a number of times, it can nicely
|
|
speed up the build process.
|
|
|
|
+ccache+ support is integrated in Buildroot. You just have to enable
|
|
+Enable compiler cache+ in +Build options+. This will automatically
|
|
build +ccache+ and use it for every host and target compilation.
|
|
|
|
The cache is located in +$HOME/.buildroot-ccache+. It is stored
|
|
outside of Buildroot output directory so that it can be shared by
|
|
separate Buildroot builds. If you want to get rid of the cache, simply
|
|
remove this directory.
|
|
|
|
You can get statistics on the cache (its size, number of hits,
|
|
misses, etc.) by running +make ccache-stats+.
|