9754b91c1
Mike Frysinger
2005-09-02
Subject
touchup some grammar, formatting, and remove some outdated notes
SOURCE BUG
This commit was genuinely broken at the time (not related to our build system): scripts/config/mkconfigs.c (2005-08-01 - 2006-10-05 arasi) uretilen bbconfigopts.h icine .config satirlarini kacissiz, ham newline'larla gömüyordu - gecerli C degildi, busybox'un kendi bb_mkdep araci bile parse edemiyordu (7d219aab7 ile duzeltildi, mkconfigs shell scripte cevrildi)
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/new-applet-HOWTO.txt+17 -12
| @@ -11,10 +11,11 @@ Thomas Lundquist - Added stuff for the new directory layout. | |
| Initial Write | |
| ------------- | |
| - | First, write your applet. Be sure to include copyright information at the |
| - | top, such as who you stole the code from and so forth. Also include the |
| - | mini-GPL boilerplate. Be sure to name the main function <applet>_main instead |
| - | of main. And be sure to put it in <applet>.c. Usage do not have to be taken care of by your applet. |
| + | First, write your applet. Be sure to include copyright information at the top, |
| + | such as who you stole the code from and so forth. Also include the mini-GPL |
| + | boilerplate. Be sure to name the main function <applet>_main instead of main. |
| + | And be sure to put it in <applet>.c. Usage does not have to be taken care of by |
| + | your applet. |
| For a new applet mu, here is the code that would go in mu.c: | |
| @@ -78,8 +79,7 @@ As you are writing your applet, please be aware of the body of pre-existing | |
| useful functions in libbb. Use these instead of reinventing the wheel. | |
| Additionally, if you have any useful, general-purpose functions in your | |
| - | program that could be useful in another program, consider putting them in |
| - | libbb. |
| + | applet that could be useful in other applets, consider putting them in libbb. |
| Placement / Directory | |
| @@ -90,11 +90,11 @@ Find the appropriate directory for your new applet. | |
| Make sure you find the appropriate places in the files, the applets are | |
| sorted alphabetically. | |
| - | Add the applet to Makefile.in in the chosen applet directory: |
| + | Add the applet to Makefile.in in the chosen directory: |
| obj-$(CONFIG_MU) += mu.o | |
| - | Add the applet to Config.in in the chosen applet directory: |
| + | Add the applet to Config.in in the chosen directory: |
| config CONFIG_MU | |
| bool "MU" | |
| @@ -116,6 +116,7 @@ This should look like the following: | |
| "Options:\n" \ | |
| "\t-a\t\tfirst function\n" \ | |
| "\t-b\t\tsecond function\n" \ | |
| + | ... |
| If your program supports flags, the flags should be mentioned on the first | |
| line (-[abcde]) and a detailed description of each flag should go in the | |
| @@ -149,10 +150,14 @@ Adding some text to docs/Configure.help is a nice start. | |
| The Grand Announcement | |
| ---------------------- | |
| - | Then create a diff -urN of the files you added (<appletdir/><applet>.c, |
| - | include/usage.c, include/applets.h, include/config.h, <appletdir>/Makefile.in, <appletdir>/config.in) |
| + | Then create a diff -urN of the files you added and/or modified. Typically: |
| + | <appletdir>/<applet>.c |
| + | include/usage.c |
| + | include/applets.h |
| + | <appletdir>/Makefile.in |
| + | <appletdir>/config.in |
| and send it to the mailing list: | |
| - | [email protected]. |
| + | [email protected] |
| + | http://busybox.net/mailman/listinfo/busybox |
| Sending patches as attachments is preferred, but not required. | |
| - | |