1 2 3 4 5 6 7 8 9 10 11
12 /*!
13 * ======== Main ========
14 * Graphical interface to path tool
15 *
16 * This graphical interactive tool displays the packages located along any
17 * specified package repository path.
18 *
19 * At startup, this tool shows the packages located along the current package
20 * path; i.e.,
21 * @p(code)
22 * $XDCPATH;$XDCROOT/packages;^
23 * @p
24 *
25 * where `$XDCPATH` is the value of the the user settable prefix of the
26 * package path, `$XDCROOT` is the installation directory of the XDC tools,
27 * and `^` is the repository of the package in the current working directory
28 * (if it exists). To specify a package path other than the current package
29 * path, use the --packagepath option. Only semicolon delimited canonical
30 * paths should be specifed as arguments with the --packagepath option.
31 * Environment variables such as $XDCROOT and special designators such as
32 * '^' should not be used.
33 *
34 * @b(Usage)
35 * @p(code)
36 * xs xdc.tools.path.sg [--packagepath PATH]
37 * @p
38 *
39 * @a(Bugs)
40 *
41 * This tool scans all packages available along the current
42 * package path before displaying the user interface. So, a repository in
43 * the package path that contains a large number of sub-directories, such
44 * as '/', causes very long delays before the user interface is displayed.
45 *
46 * While it is easy to see that you should not put '/' in the package path,
47 * it is less obvious that installing a package at '/' has the same effect.
48 */
49 metaonly module Main inherits xdc.tools.ICmd {
50
51 override config String usage[] = [
52 '[--packagepath PATH]'
53 ];
54
55 /*!
56 * ======== createPartControl ========
57 * @_nodoc
58 */
59 function createPartControl(parent);
60
61 instance:
62
63 //! package path to scan for packages
64 @CommandOption('packagepath')
65 config string pathArg = null;
66
67 }
68 69 70
71