1mdtool(1) General Commands Manual mdtool(1)
2
6 mdtool - MonoDevelop Application Runner
7
9 mdtool <applicationId> ...
10 mdtool setup ...
12 mdtool -q
14
16 mdtool is a tool that can execute head-less MonoDevelop applications,
17 this can be used for example to do batch compilations without starting
18 up the MonoDevelop GUI.
19
21 applicationId ...
22 Runs the specified application.
23 -q Lists available applications.
25
27 The list of applications returned by the option -q might be different
28 depending on which add-ins are installed.
29 gsetup Graphical add-in setup utility.
31 build [options] [project-file]
33 Project build tool. Use this tool to build any solution sup‐
34 ported by MonoDevelop (eg. .mds, .sln). If no solution/project
35 is specified then it will pull the first solution it can find in
36 the current directory. You can use this option to build pack‐
37 ages in a head-less or batch fashion.
38 Options
40 -c , --configuration:CONFIGURATION Name of the solution
41 configuration to build.
42 -t , --target:TARGET Name of the target: Clean or Build
44 -p , --project:PROJECT Name of the project to build.
46 dbgen Parser database generation tool.
49 project-export
51 Project conversion tool.
52 IDE The MonoDevelop IDE.
55 generate-makefiles <solution-file> [--simple-makefiles] [-d:default-
58 config]
59 Makefile generator tool. This can be used to generate makefiles
60 from any solution supported by MonoDevelop.
61 Options
63 --simple-makefiles , -s Generates set of Makefiles with
64 the most common targets, and a configuration script that
65 does a basic check of package dependencies. Default is to
66 generate Makefile structure based on Autotools with the
67 standard targets and configuration scripts.
68 -d:default-config Configuration that the Makefile will
70 build by default. Other configurations can be selected
71 via the '--config' or '--enable-*' option of the gener‐
72 ated configure script.
73 setup command [arg1, .., argn2]
76 Runs the MonoDevelop add-in setup command. You must specify a
77 command to execute. If none is provided a list of commands is
78 displayed
79 Add-in Commands
80 install (i) [package-name|package-file] Installs an add-
81 in or set of addins. The command argument is a list of
82 files and/or package names. If a package name is provided
83 the package will be looked out in the registered reposi‐
84 tories. A specific add-in version can be specified by
85 appending it to. the package name using MonoDe‐
86 velop.SourceEditor/0.9.1
87 uninstall (u) [package-name]
89 Uninstalls an add-in. The command argument is the
90 name of the add-in to uninstall.
91 check-install (ci)
93 Checks if a package is installed. If it is not, it
94 looks for the package in the registered reposito‐
95 ries, and if found the package is downloaded and
96 installed, including all needed dependencies.
97 update (up)
99 Downloads and installs available updates for
100 installed add-ins.
101 list (l)
103 Prints a list of all installed add-ins.
104 list-av (la)
106 Prints a list of add-ins available to install in
107 the registered repositories.
108 list-update (lu)
110 Prints a list of available add-in updates in the
111 registered repositories.
112 Repository Commands
113 rep-add (ra) url1 [url2 [url2]]
115 Registers an add-in repository. Several URLs can
116 be provided.
117 rep-remove (rr) url1 [url2 [url2]]
119 Unregisters an add-in repository. Several URLs can
120 be provided.
121 rep-update (ru)
123 Updates the lists of addins available in all reg‐
124 istered repositories.
125 rep-list (rl)
127 Shows a list of all registered repositories.
128 Add-in Registry Commands:
129 reg-update (rgu)
131 Looks for changes in add-in directories and
132 updates the registry. New add-ins will be added
133 and deleted add-ins will be removed.
134 reg-build (rgu)
136 info [filename|package-name]
138 Prints information about an add-in.
139 Packaging Commands
140 rep-build (rb) path
142 Scans the provided directory and generates a set
143 of index files with entries for all add-in pack‐
144 ages found in the directory tree. The resulting
145 file structure is an add-in repository that can be
146 published in a web site or a shared directory.
147 pack (p) file-path
149 Creates an add-in package (.mpack file) which
150 includes all files needed to deploy an add-in. The
151 command parameter is the path to the add-in's con‐
152 figuration file.
153 help (h) [command]
155 Shows help for the given command
156 Debug Commands:
157 dump-file
159 Prints the contents of a registry file for debug‐
160 ging.
161
163 monodevelop(1), mono(1), mcs(1)
164
166 Copyright (C) 2007 Novell, Inc (http://www.novell.com)
167
169 Visit http://lists.ximian.com/mailman/listinfo/monodevelop-list for
170 details.
171
173 Visit http://www.monodevelop.com for details
174 mdtool(1)