diff options
| author | Samuel Martin <s.martin49@gmail.com> | 2012-11-11 03:14:42 +0000 |
|---|---|---|
| committer | Peter Korsgaard <jacmet@sunsite.dk> | 2012-11-15 23:58:38 +0100 |
| commit | 5e84b8b73cc32b307642917c70bc3186c1ffd69b (patch) | |
| tree | 55611c603694d41813d0e7c219a0a2e28c5197a8 /docs/manual/adding-packages-directory.txt | |
| parent | 17feaf00160de8f68b647092e0849e77866fb4dc (diff) | |
| download | buildroot-novena-5e84b8b73cc32b307642917c70bc3186c1ffd69b.tar.gz buildroot-novena-5e84b8b73cc32b307642917c70bc3186c1ffd69b.zip | |
manual: rework the whole documentation stub
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>
Diffstat (limited to 'docs/manual/adding-packages-directory.txt')
| -rw-r--r-- | docs/manual/adding-packages-directory.txt | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt index 4a96415ad..6030e0852 100644 --- a/docs/manual/adding-packages-directory.txt +++ b/docs/manual/adding-packages-directory.txt @@ -1,5 +1,7 @@ +// -*- mode:doc; -*- + Package directory ------------------ +~~~~~~~~~~~~~~~~~ First of all, create a directory under the +package+ directory for your software, for example +libfoo+. @@ -10,7 +12,7 @@ one of these categories, then create your package directory in these. +Config.in+ file -~~~~~~~~~~~~~~~~ +^^^^^^^^^^^^^^^^ Then, create a file named +Config.in+. This file will contain the option descriptions related to our +libfoo+ software that will be used @@ -146,7 +148,7 @@ so, the dependency also needs to be expressed in the +.mk+ file of the package. The +.mk+ file -~~~~~~~~~~~~~~ +^^^^^^^^^^^^^^ Finally, here's the hardest part. Create a file named +libfoo.mk+. It describes how the package should be downloaded, configured, built, |