4 @ shell script±àдʱ£¬
\r
5 # Ê×ÏÈ¿¼ÂdzÌÐò¹¦ÄÜÐÔ£¬ÒÔ¼°´úÂëʵÏֵĿò¼Ü
\r
6 # Æä´Î¸ù¾ÝÔËÐУ¬½øÐÐÓÅ»¯ºÍµ÷Õû¡£
\r
7 # ¸ù¾ÝÐèÒª£¬±àдbinary-code¡£
\r
13 @ build-pkg: for pkg compile.
\r
14 @ codegen: for code generating from .catalog file or other graphical design
\r
15 files. and sync code back to the design file.
\r
16 @ devtask: for task schedule.
\r
17 @ tagdoc: for demand record.
\r
18 @ codefmt: for code formatting.
\r
19 @ *staruml/umbrello/umlet/dia/eclipse: one of the tool to draw diagrams.
\r
20 @ *CSSC: for local file version management. append remote updata feature to be
\r
21 a general version management tool.
\r
22 @ gendocs.sh: utility in GNU lib.
\r
30 @ Ò»¸öͨÓõÄlib»ò³ÌÐò£¬¹¦Äܾ¡Á¿µ¥Ò»£¬¶ÔÖ÷Òª¹¦ÄܽøÐÐÍêÉÆ£¬¹¦ÄܵÄÀ©Õ¹ÔÚÆäËülib»òÆäËü´úÂëÖÐʵÏÖ£¬±ÜÃ⹦ÄÜÇ÷ÓÚÍêÉƵÄͬʱ£¬´úÂë±äµÃÓ·Öס£
\r
31 ¶ÔÓÚÒ»¸öÏà¶ÔÍêÉƵŦÄÜÄ£¿éµÄsrc-pkg£¬´úÂëµÄ¸üÐÂrules£º
\r
32 # ´úÂëÄ£¿é»¯£¬³ÌÐò¿É¶ÁÐÔ£¬ÈõñîºÏÐÔ£¬´øÀ´µÄ³ÌÐò½á¹¹¸Ä½ø£»
\r
33 # bugÐÞ¸´£¬Îĵµ¸üУ»
\r
34 # ÔËÐл·¾³±ä»¯£¬ÒÀÀµÈí¼þ¸üУ»
\r
35 # ÔËÐÐÐÔÄܸĽø£¬´úÂëÌå»ý¾«¼ò£¬×ÊԴʹÓøĽø£»
\r
36 # ¹¤³Ì±àÒë¸Ä½ø£¬´úÂë¹¹½¨¹¤¾ß¸Ä½ø¡£
\r
37 @ й¦ÄܵÄÔö¼Ó´øÀ´µÄ´úÂë¸üУ¬Ê¹ÓÃnew-branch£¬ÔÚ¹¦Äܱàдºó£¬¸üÐÂÖ÷°æ±¾ºÅ£¬»òÕßн¨Ò»¸öÈí¼þ°ü¡£
\r
39 @ Ëæ×ÅÈí¼þµÄ¿ª·¢£¬´úÂ빦ÄܵÄÔö¼Ó£¬´úÂë»á±È½ÏÓ¹Öס£Ð¹¦ÄܵÄÌí¼Ó£¬ÓÐʱ¿ÉÒÔÁíÒ»¸öÈí¼þ°üµÄÐÎʽÌí¼Ó¡£ÀýÈçshell³ÌÐòµÄ¹¦ÄܵÄÌí¼Ó£¬Óëscript grammerÏà¹ØµÄ¹¦ÄÜ£¬ÔÚshell³ÌÐòÖÐÌí¼Ó£¬Ò»Ð©buildin³ÌÐò£¬ÒÔpluginÐÎʽÔÚÆäËüÈí¼þ°üÖС£cmdhintÕâÀ๦Äܵ÷Õûshell³ÌÐòµÄ³ÌÐò½á¹¹£¬cmdhint¹¦ÄÜÔÚÁíÍâµÄÈí¼þ°üÖÐÌí¼Ó¡£Õâʹshell³ÌÐò±È½Ï¾«¼ò£¬ÆäËü¹¦ÄÜÊÇextensiableµÄ¡£ËùÒÔ³ÌÐòµÄplugin¹¦ÄܱȽÏÓÐÓã¬ÓÃÓÚ³ÌÐòµÄextend¡£
\r
40 @ »ù´¡lib£¬libcxtÖ®ÀàµÄ¹¦ÄÜfeature½Ï·á¸»¡£¶øһЩuserʹÓõijÌÐò£¬ÀýÈçÒ»¸ödownloadÈí¼þ£¬Ïà¶ÔÆäËüÈí¼þ£¬¹¦ÄܺÍfeatueÐèÒªÏà¶ÔÈõһЩ£¬¹¦Äܲ»ÄÇôÍêÉÆ¡£
\r
41 # Ó¦ÓóÌÐòÊÇlib¿âµÄexample£¬Í¬Ê±Ò²ÓÃÓÚ»ù±¾µÄʹÓá£Ê¹lib¿â½ÏÈÝÒ×ÔÚÆäËü³ÌÐòÖÐʹÓ㬶øÓ¦ÓóÌÐòʹÈí¼þÓÐһЩ¹¦ÄÜ£¬¿ÉÓá£
\r
42 # libÇ÷ÓÚ¹¦ÄÜÍêÉÆ£¬appÇ÷ÓÚstable¡¢feature-less¡¢res-cost-less¡¢tiny¡£
\r
43 # ÒÔÐÂÔö¿âÎļþ»òÈí¼þ°üÌí¼Óй¦ÄÜ£¬µ¥¸öÈí¼þ°ü¹¦Äܾ¡Á¿Ç÷Óڹ̶¨£¬¶ø·ÇƵ·±µÄÈí¼þ°æ±¾¸üС£
\r
46 @ ³ÌÐò¿ª·¢µÄ¹¦ÄÜ×é¼þ»¯
\r
47 Ò»¸öÓ¦ÓóÌÐòÒÔpluginµÄÐÎʽÌṩ£¬ÔÚÒ»¸öexecutableÖÐÔËÐС£
\r
51 @ pkg-builder£¨°üÀ¨build-pkg¡¢CCompilerCollection¡¢build-config¡¢build-pkglist£©ÓÃÓÚ²Ù×÷ϵͳµÄÈí¼þ°üµÄ±àÒë¡¢¿ª·¢ºÍ×éÖ¯¡£
\r
52 Ïà½üÓÚdebianµÄ¿ª·¢¹¤¾ß£¬µ«¾ßÓиüºÃµÄÈõñîºÏÐÔ¡£debian¿ª·¢¹¤¾ßÖÐʹÓý϶àÀàÐ͵Ľű¾£¬sh¡¢perl¡¢python¡¢tclµÈ£¬Õâ¶ÔÓÚÓ¦Óÿª·¢À´ËµÏà¶ÔÒ×ʹÓ㬶ø¶ÔÓÚ²Ù×÷ϵͳµÄ»ù´¡Èí¼þ°ü£¬pkg-builderµÄ·½·¨¸üΪʵÓá£
\r
54 @ base program language knownlege. some problem not only use if/else/for/while
\r
55 to implement feature, use general public knownlege technolege to writing
\r
56 code. eg: data-structure, windows-system-api,
\r
59 # project templete. dir structure of a src pkg sould include src-code, testing, man-doc/API-doc, user-manual-doc and so on. or use the templete project.
\r
60 # src code templete. a src file should include file info header, language feature seperating comment. use tmpl or codegen to generate
\r
61 src code framework, instead of writing manually.
\r
63 @ a src pkg use standard/default/general config/data file format, such as imi/catalog/xml/rec/csv/db.
\r