Changeset 61 for trunk/doc/kmkdocs.c
- Timestamp:
- Dec 14, 2003, 12:18:38 AM (22 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/kmkdocs.c
r19 r61 48 48 * 49 49 * 50 * @subsection The Micro Shell51 *52 * The micro shell provides the basic shell functionality kBuild need - no more,53 * no less. It is intended to be as simple as possible.54 *55 * The shell commands are case sensitive - all lowercase.56 *57 * The shell environment variables are case sensitive or insensitive according to58 * host os.59 *60 *61 *62 * @subsubsection Command Separators63 *64 * There is one command separator '&&'. This works like splitting the command line65 * into several makefile lines. This splitting isn't done by the micro shell but66 * the makefile interpreter.67 *68 * You might thing this is limiting, but no, you can use all the makefile command69 * prefixes.70 *71 *72 *73 * @subsubsection Path Component Separator (/)74 *75 * The shell uses '/' as path component separator.76 * For host OSes with the notion of drive letters or similar, ':' is77 * used to separate the drive letter and the path.78 *79 *80 *81 * @subsubsection UNC paths82 *83 * For host OSes which supports UNC paths these are supported but for the chdir84 * command.85 *86 * The Path Component Separator is still '/' for UNC paths.87 *88 *89 *90 * @subsubsection Wildchars91 *92 * '*' and '?' are accepted as wildchars.93 *94 * '*' means 0 or more characters. <br>95 * '?' means 1 character.96 *97 * When the term 'pattern' is use in command description this means that98 * wildchars are accepted.99 *100 *101 *102 * @subsubsection Quoting103 *104 * Use double quotes (") to quote filenames or executables containing spaces.105 *106 *107 *108 * @subsubsection Execute Program109 *110 * If the first, possibly quoted, word of a commandline if not found as an111 * internal command will be tried executed. If no path it will be searched112 * for in the PATH environment variable.113 *114 *115 *116 * @subsubsection Commands117 *118 * This section will describe the commands implemented by the shell.119 *120 *121 *122 * @subsubsubsection copy123 * Copies one or more files to a target file or directory.124 *125 * <b>Syntax: copy <source file pattern> [more sources] <target> </b>126 *127 * Specify one or more source file patterns.128 *129 * Specify exactly one target. The target may be a directory or a file.130 * If it's a file and multiple source files specified either thru pattern or131 * multiple source file specifications, the target file will be a copy of the132 * last one.133 *134 * The command fails if a source file isn't found. It also fails on read or135 * write errors.136 *137 *138 *139 * @subsubsubsection copytree140 * Copies one or more files to a target file or directory.141 *142 * <b>Syntax: copytree <source directory> <target directory> </b>143 *144 * Specify exactly one source directory.145 *146 * Specify exactly one target directory. The target directory path will be147 * created if doesn't exist.148 *149 * The command fails if source directory isn't found. It also fails on read or150 * write errors.151 *152 *153 *154 * @subsubsubsection rm155 * Deletes one or more files.156 *157 * <b>Syntax: rm [file pattern] [more files] </b>158 *159 * Specify 0 or more file patterns for deletion.160 *161 * This command fails if it cannot delete a file. It will not fail if a file162 * doesn't exist. It will neither fail if no files are specified.163 *164 *165 *166 * @subsubsubsection rmtree167 * Deletes one or more directory trees.168 *169 * <b>Syntax: rmtree [directory pattern] [directories] </b>170 *171 * Specify 0 or more directory patterns for deletion.172 *173 * This command fails if it cannot delete a file or directory. It will not fail174 * if a directory doesn't exist. It will neither fail if no files are specified.175 *176 *177 *178 * @subsubsubsection chdir179 * Changes the current directory.180 *181 * This updates the .CWD macro to the new current directory path.182 *183 * <b>Syntax: chdir <directory> </b>184 *185 *186 *187 * @subsubsubsection mkdir188 * Create directory.189 *190 * <b>Syntax: mkdir <directory> </b>191 *192 * Specify one directory to create.193 *194 *195 *196 * @subsubsubsection rmdir197 * Remove directory.198 *199 * <b>Syntax: rmdir <directory> </b>200 *201 * Specify one directory to remove. The directory must be empty.202 *203 * This command failes if directory isn't empty. It will not fail if204 * the directory doesn't exist.205 *206 *207 *208 * @subsubsubsection set209 * Set environment variable.210 *211 * <b>Syntax: set <envvar>=<value> </b>212 *213 *214 *215 * @subsubsubsection unset216 * Unset enviornment variable(s).217 *218 * <b>Syntax: unset <envvar pattern> [more envvars] </b>219 *220 * Specify on or more environment variable patterns.221 *222 *223 *224 * @subsubsubsection pushenv225 * Pushes a set of environment variables onto the environment stack. The226 * variables can later be popped back using the popenv command.227 *228 * If '*' is specified as pattern the complete enviornment is pushed and229 * when popped it will <b>replace</b> the enviornment.230 *231 * <b>Syntax: pushenv <envvar pattern> [more envvars] </b>232 * <b>Syntax: pushenv * </b>233 *234 *235 *236 * @subsubsubsection popenv237 * Pop a set of environment variables from the environment stack. If a '*'238 * push was done, we'll replace the enviornment with the variables poped off239 * the stack.240 *241 * <b>Syntax: popenv </b>242 *243 *244 *245 * @subsubsubsection echo246 * Prints a message to stdout.247 *248 * <b>Syntax: echo <level> <message>249 *250 * Level is verbosity level of the message. This is compared with the251 * KBUILD_MSG_LEVEL environment variable. The message is suppressed if the252 * level is lower that KBUILD_MSG_LEVEL.253 *254 * The message can be empty. Then a blank line will be printed.255 *256 *257 50 * 258 51 */
Note:
See TracChangeset
for help on using the changeset viewer.