[BusyBox] new-applet-HOWTO diff.

Thomas Lundquist lists at zelow.no
Mon Sep 29 07:15:47 UTC 2003


I've been playing around with an attempt to make a add-applet
perl script but all I've gotten out of it so far is a diff of
new-applet-HOWTO.txt, the files are alot more complex than 
I hoped for.

but it should be updated according to the newest structure.

cvs diff docs/new-applet-HOWTO.txt 

attatched.



Thomas.
-------------- next part --------------
Index: docs/new-applet-HOWTO.txt
===================================================================
RCS file: /var/cvs/busybox/docs/new-applet-HOWTO.txt,v
retrieving revision 1.7
diff -r1.7 new-applet-HOWTO.txt
17,18c17,19
< of main.  And be sure to put it in <applet>.c.  For a new applet mu, here is
< the code that would go in mu.c:
---
> of main.  And be sure to put it in <applet>.c. Usage do 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:
89c90,93
< Add the applet to the applet directory Makefile:
---
> 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:
93c97
< Add the applet to the applet directory config.in:
---
> Add the applet to Config.in in the chosen applet directory:
95c99,103
< bool 'mu'          CONFIG_MU
---
> config CONFIG_MU
> 	bool "MU"
> 	default n
> 	help
> 	  Returns an indeterminate value.
132c140
< Finally, add a define for your applet to Config.h:
---
> Finally, add a define for your applet to include/config.h
134c142
< 	#define CONFIG_MU
---
> 	#undef CONFIG_MU
149,152c157,160
< Then create a diff -urN of the files you added (<applet>.c, usage.c,
< applets.h, Config.h) and send it to the mailing list:
< busybox at busybox.net. Sending patches as attachments is preferred, but
< not required.
---
> 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) 
> and send it to the mailing list:
> busybox at busybox.net. 
153a162
> Sending patches as attachments is preferred, but not required.


More information about the busybox mailing list