odk/docs/tools.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
   2 <!--
   3  * This file is part of the LibreOffice project.
   4  *
   5  * This Source Code Form is subject to the terms of the Mozilla Public
   6  * License, v. 2.0. If a copy of the MPL was not distributed with this
   7  * file, You can obtain one at http://mozilla.org/MPL/2.0/.
   8  *
   9  * This file incorporates work covered by the following license notice:
  10  *
  11  *   Licensed to the Apache Software Foundation (ASF) under one or more
  12  *   contributor license agreements. See the NOTICE file distributed
  13  *   with this work for additional information regarding copyright
  14  *   ownership. The ASF licenses this file to you under the Apache
  15  *   License, Version 2.0 (the "License"); you may not use this file
  16  *   except in compliance with the License. You may obtain a copy of
  17  *   the License at http://www.apache.org/licenses/LICENSE-2.0 .
  18 -->
  19 <html>
  20 <head>
  21   <title>LibreOffice %PRODUCT_RELEASE% SDK - Development Tools</title>
  22   <link rel="stylesheet" type="text/css" href="sdk_styles.css">
  23   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  24   <meta name="author" content="J&uuml;rgen Schmidt">
  25 </head>
  26 <body>
  27         <a name="tools"></a>
  28         <div id="BgContainer">
  29             <div id="Container">
  30                 <div id="TopHeader">
  31                     <a id="Logo" href="http://www.libreoffice.org/" title="Go to the Home of LibreOffice and the LibreOffice Community page"></a>
  32                     <p id="HeaderTagLine">
  33                         Software Development Kit %PRODUCT_RELEASE%
  34                     </p>
  35                 </div>
  36                 <div class="clear">
  37                 </div>
  38                 <div id="Layout">
  39                     <div class="typography">
  40                         <h1>
  41                             Development Tools
  42                         </h1>
  43 <table class="table1" cellpadding=0>
  44   <tr>
  45     <td colspan="3"><img  class="nothing10" src="images/nada.gif"></td>
  46   </tr>
  47   <tr>
  48     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
  49     <td>
  50       <table class="table2">
  51             <tr>
  52                   <td colspan="3"><img class="nothing1" src="images/nada.gif"></td>
  53         </tr>
  54         <tr>
  55           <td>
  56           <table class="table3">
  57             <tr valign="top">
  58               <td class="content3"><img src="images/arrow-1.gif"></td>
  59               <td><a href="#unopkg"  title="link to the unopkg tool description">unopkg</a></td>
  60               <td class="content87">The new UNO package deployment tool. It comes
  61                           with the office installation and can be found in the program
  62                           directory of the office installation.</td>
  63             </tr>
  64             <tr valign="top">
  65               <td class="content3"><img src="images/arrow-1.gif"></td>
  66               <td><a href="#unoexe"  title="link to the uno tool description">uno</a></td>
  67               <td class="content87">Tool to provide a UNO runtime environment and
  68                           provide configured (deployed) or single components. This tool
  69                           comes with the office installation and can be found in the program
  70                           directory of the office installation.</td>
  71             </tr>
  72            <tr valign="top">
  73               <td class="content3"><img src="images/arrow-1.gif"></td>
  74               <td><a href="#regmerge"  title="link to the regmerge tool description">regmerge</a></td>
  75               <td class="content87">Tool to merge several registry (e.g. type
  76                           libraries) files into one file. <b>Note:</b> Since OpenOffice.org 3 it is not longer part of the SDK but it comes directly with the office as part of the <b>ure</b>.</td>
  77             </tr>
  78             <tr valign="top">
  79               <td class="content3"><img src="images/arrow-1.gif"></td>
  80               <td><a href="#regview"  title="link to the regview tool description">regview</a></td>
  81               <td class="content87">Tool to view the content of a registry file
  82                           in a human readable manner. Special support for type library
  83                           nodes. <b>Note:</b> Since OpenOffice.org 3 it is not longer part of the SDK but it comes directly with the office as part of the <b>ure</b>.</td>
  84             </tr>
  85             <tr valign="middle">
  86               <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
  87             </tr>
  88             <tr valign="top">
  89               <td class="content3"><img src="images/arrow-1.gif"></td>
  90               <td><a href="#idlc" title="link to the idlc tool description">idlc</a></td>
  91               <td class="content87">The UNOIDL compiler, generates a common
  92                           binary type library format as base for all codemaker tools and
  93                           the UNO runtime type library.</td>
  94             </tr>
  95             <tr valign="top">
  96               <td class="content3"><img src="images/arrow-1.gif"></td>
  97               <td><a href="#cppumaker" title="link to the cppumaker tool description">cppumaker</a></td>
  98               <td class="content87">Tool for generating C++ code for the UNOIDL
  99                           types stored in a type library.</td>
 100             </tr>
 101             <tr valign="top">
 102               <td class="content3"><img src="images/arrow-1.gif"></td>
 103               <td><a href="#javamaker" title="link to the javamaker tool description">javamaker</a></td>
 104               <td class="content87">Tool for generating Java class files for the
 105                           UNOIDL types stored in a type library.</td>
 106             </tr>
 107            <tr valign="top">
 108               <td class="content3"><img src="images/arrow-1.gif"></td>
 109               <td><a href="#climaker" title="link to the climaker tool description">climaker</a></td>
 110               <td class="content87">Tool for generating CLI assemblies for the
 111                           UNOIDL types stored in a type library (windows only).</td>
 112             </tr>
 113             <tr valign="top">
 114               <td class="content3"><img src="images/arrow-1.gif"></td>
 115               <td><a href="#uno-skeletonmaker" title="link to the uno-skeletonmaker tool description">uno-skeletonmaker</a></td>
 116               <td class="content87">Tool for dumping type definitions on stdout or generating complete code skeletons for Java/C++.</td>
 117             </tr>
 118             <tr valign="top">
 119               <td class="content3"><img src="images/arrow-1.gif"></td>
 120               <td><a href="#regmerge"  title="link to the regmerge tool description">regmerge</a></td>
 121               <td class="content87">Tool to merge several registry (e.g. type
 122                           libraries) files into one file.</td>
 123             </tr>
 124             <tr valign="top">
 125               <td class="content3"><img src="images/arrow-1.gif"></td>
 126               <td><a href="#regview"  title="link to the regview tool description">regview</a></td>
 127               <td class="content87">Tool to view the content of a registry file
 128                           in a human readable manner. Special support for type library
 129                           nodes.</td>
 130             </tr>
 131             <tr valign="top">
 132               <td class="content3"><img src="images/arrow-1.gif"></td>
 133               <td><a href="#autodoc"  title="link to the autodoc tool description">autodoc</a></td>
 134               <td class="content87">Tool to generate javadoc-like documentation
 135                           for C/C++ and UNOIDL files.</td>
 136             </tr>
 137             </table>
 138           </td>
 139                 </tr>
 140       </table>
 141     </td>
 142         <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 143   </tr>
 144   <tr>
 145     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 146   </tr>
 147   <tr>
 148     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 149     <td>
 150       <table class="table2">
 151         <tr>
 152                   <td colspan="2" class="head1"><a name="unopkg"/>unopkg</td>
 153                   <td align="right">
 154                         <a style="a:link:visited #FFFFFF;" href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 155                         <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a></td>
 156         </tr>
 157                 <tr>
 158                   <td colspan="3">
 159                   <p>'unopkg' is a tool for easy deployment of UNO packages in an existing
 160                   office installation. UNO packages are UNO components (single libraries or
 161                   Jar files or more complex zip files that contains one or more libraries|
 162                   Jar files, type libraries and configuration items), scripts  and
 163                   LibreOffice %PRODUCT_RELEASE% Basic libraries as zip package. 'unopkg' is not part of the
 164                   SDK but comes with the office directly and is a development tool as well
 165                   as an end user tool to deploy extension into an office installation.</p>
 166                   <p>More details concerning deployment and this tool can be find in the
 167                   Developer's Guide: <a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/unopkg" title="link to the &quot;Extension Manager - unopkg&quot; chapter in the Developer's Guide">Extension Manager - <i>unopkg</i></a>.</p>
 168                   <p><b>Note:</b> This tool works only in the <i>&lt;office&gt;/program</i>
 169                   directory!</p>
 170                   <p class="head2">Usage:</p>
 171                   <blockquote>
 172                   <b><code>
 173                     unopkg add &lt;options&gt; package-path...<br>
 174                         unopkg remove &lt;options&gt; package-name...<br>
 175                         unopkg list &lt;options&gt; package-name...<br>
 176                         unopkg reinstall &lt;options&gt;<br>
 177                         unopkg gui<br>
 178                         unopkg -V<br>
 179                         unopkg -h<br>
 180                   </code></b>
 181                   </blockquote>
 182                   <p class="head2">Sub-commands:</p>
 183                   <p>
 184                   <table class="table4">
 185                   <tr>
 186                     <td class="cell15"><code>add</code></td>
 187                         <td class="cell85">add packages</td>
 188                   </tr>
 189                         <tr>
 190                         <td class="cell15"><code>remove</code></td>
 191                         <td class="cell85">remove packages by name</td>
 192           </tr>
 193                   <tr>
 194             <td class="cell15"><code>reinstall</code></td>
 195                         <td class="cell85">export feature: reinstall all deployed
 196                         packages</td>
 197           </tr>
 198                   <tr>
 199             <td class="cell15"><code>list</code></td>
 200                         <td class="cell85">list information about deployed packages</td>
 201           </tr>
 202                   <tr>
 203             <td class="cell15"><code>gui</code></td>
 204                         <td class="cell15">raise Package Manager Graphical User Interface
 205                         (GUI)</td>
 206           </tr>
 207                   </table>
 208                   </p>
 209                   <p class="head2">Options:</p>
 210                   <p>
 211                   <table class="table4">
 212                   <tr>
 213             <td class="cell15"><code>-h, --help</code></td>
 214             <td class="cell85">show this help on the command line</td>
 215           </tr>
 216                   <tr>
 217             <td class="cell15"><code>-V, --version</code></td>
 218                         <td class="cell85">shows version information
 219                         </td>
 220           </tr>
 221           <tr>
 222             <td class="cell15"><code>-v, --verbose</code></td>
 223                         <td class="cell85">dump verbose output to stdout</td>
 224           </tr>
 225                   <tr>
 226             <td class="cell15"><code>-f, --force</code></td>
 227                         <td class="cell85">force overwriting existing packages</td>
 228           </tr>
 229           <tr>
 230             <td class="cell15"><code>--log-file &lt;file&gt;</code></td>
 231                         <td class="cell85">custom log file; default:
 232                         <i>&lt;cache-dir&gt/log.txt</i>.</td>
 233           </tr>
 234           <tr>
 235             <td class="cell15"><code>--shared</code></td>
 236                         <td class="cell85">expert feature: operate on shared installation
 237                         deployment context; run only when no concurrent Office process(es) are
 238                         running!</td>
 239           </tr>
 240           <tr>
 241                     <td class="cell15"><code>--deployment-context &lt;context&gt</code>
 242                         </td>
 243                         <td class="cell85">expert feature: explicit deployment context</td>
 244           </tr>
 245                   </table>
 246                   </p>
 247                   </td>
 248                 </tr>
 249       </table>
 250     </td>
 251         <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 252   </tr>
 253   <tr>
 254     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 255   </tr>
 256   <tr>
 257     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 258     <td>
 259       <table class="table2">
 260         <tr>
 261                   <td colspan="2" class="head1"><a name="unoexe"/>uno</td>
 262                   <td align="right">
 263                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 264                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 265                   </td>
 266         </tr>
 267                 <tr>
 268                   <td colspan="3">
 269                   <p>The UNO-starter is for running a component or service process, and
 270                   providing a runtime environment. Raising a component might look like
 271                   this </p>
 272                   <p><code>[c:\] uno.exe -c MyComponent -l mycomp.dll -r myregistry.rdb
 273                   -- foo bar</code></p>
 274                   <p>or</p>
 275                   <p><code>[c:\] uno.exe -s foo.bar.FooBarService -r myregistry.rdb
 276                   -- foo bar</code></p>
 277                   <p>The starter loads the component and instantiates it. The component
 278                   must export the interface <a href="common/ref/com/sun/star/lang/XMain.html" title="link into the IDL reference to the interface com.sun.star.lang.XMain">com.sun.star.lang.XMain</a>:</p>
 279                   <p>
 280                   <code>interface XMain : com::sun::star::uno::XInterface <br>
 281             { <br>
 282               &nbsp;&nbsp;&nbsp; /** This method is called to run the component.<br>
 283               &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
 284               &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; @param aArguments command line arguments <br>
 285               &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; @return process error code to be returned to system <br>
 286               &nbsp;&nbsp;&nbsp; */ <br>
 287               &nbsp;&nbsp;&nbsp; long run( [in] sequence&lt; string &gt; arguments ); <br>
 288             };
 289           </code>
 290                   </p>
 291                   <p>Method run() will be called and returns the error code given, back
 292                   to the system. If the uno starter is executed with the -u (URL) option,
 293                   then XInitialization is used instead of XMain. The -u option is described
 294                   later.</p>
 295                   <p class="head2">Usage:</p>
 296                   <blockquote>
 297                   <b><code>uno (-c&lt;ComponentImplementationName&gt; -l &lt;LocationUrl&gt;
 298                     | -s &lt;ServiceName&gt;) <br>
 299             [-u uno:(socket[,host=&lt;HostName&gt;][,port=&lt;nnn&gt;]|pipe[,name=&lt;PipeName&gt;]);iiop|urp;&lt;Name&gt;<br>
 300             [--singleaccept] [--singleinstance]] <br>
 301             [-- &lt;Argument1 Argument2 ...&gt;]
 302           </code></b>
 303                   </blockquote>
 304                   <p class="head2">Options:</p>
 305                   <p>
 306                   <table class="table4">
 307           <tr>
 308             <td class="cell15"><code>&lt;HostName&gt;</code></td>
 309             <td class="cell85">Specifying a host name might be necessary to
 310                         distinguish the network interface to be used,if a machine is part of
 311                         two networks.</td>
 312           </tr>
 313           <tr>
 314             <td class="cell15"><code>&lt;PipeName&gt;</code></td>
 315             <td class="cell85">Name of a named pipe.</td>
 316           </tr>
 317           <tr>
 318             <td class="cell15"><code>&lt;Name&gt;</code></td>
 319             <td class="cell85">Identifier for demanded called component
 320                         instances.</td>
 321           </tr>
 322           <tr>
 323             <td class="cell15"><code>--singleaccept</code></td>
 324             <td class="cell85">The uno starter will accept one connection,
 325                         provide the component instance and die.</td>
 326           </tr>
 327           <tr>
 328             <td class="cell15"><code>--singleinstance</code></td>
 329             <td class="cell85">The uno starter will accept any number of
 330                         connections, but will provide the same single component instance any
 331                         time instead of creating a new instance for each connection.</td>
 332           </tr>
 333           </table>
 334                   <p><b>Service <a href="common/ref/com/sun/star/bridge/UnoUrlResolver.html" title="link into the IDL reference to the service com.sun.star.bridge.UnoUrlResolver">com.sun.star.bridge.UnoUrlResolver</a></b></p>
 335                   <p>You can easily connect to a server started with the
 336                   <code>-u (url)</code> option by using this service, giving the same url
 337                   to resolve. The service provides you an instance from remote.</p>
 338                   </p>
 339                   </td>
 340                 </tr>
 341       </table>
 342     </td>
 343     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 344   </tr>
 345   <tr>
 346     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 347   </tr>
 348   <tr>
 349     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 350     <td>
 351       <table class="table2">
 352         <tr>
 353                   <td colspan="2" class="head1"><a name="idlc"/>idlc</td>
 354                   <td align="right">
 355                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 356                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 357                   </td>
 358         </tr>
 359                 <tr>
 360                   <td colspan="3">
 361                   <p>'idlc' is the UNOIDL compiler.  It is a full featured compiler used
 362                   to check UNODL type definitions and transform valid type definitions
 363                   into a binary type library format, which is later used by all codemaker
 364                   tools. It is also used as a dynamic type library for UNO at runtime.<br>
 365                   You can find a syntax description for UNOIDL <a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/AppendixD/UNOIDL_Syntax_Specification" title="link to the &quot;UNOIDL Syntax Specification&quot; chapter in the Developer's Guide">here</a>.</p>
 366                   <p class="head2">Usage:</p>
 367                   <blockquote>
 368                   <b><code>idlc [-options] file_1 ... file_n | @&lt;filename&gt;</code></b>
 369                   </blockquote>
 370                   <p>
 371                   <table class="table4">
 372                   <tr>
 373             <td class="cell15"><code>file_1 ... file_n</code></td>
 374                         <td class="cell85">specifies one or more idl files. Only files with
 375                         the extension '.idl' are valid.</td>
 376           </tr>
 377                   <tr>
 378             <td class="cell15"><code>@&lt;filename&gt;</code></td>
 379                         <td class="cell85">filename specifies the name of a command
 380                         file.</td>
 381           </tr>
 382                   </table>
 383                   </p>
 384                   <p class="head2">Options:</p>
 385                   <p>
 386                   <table class="table4">
 387                   <tr>
 388             <td class="cell15"><code>-O&lt;path&gt;</code></td>
 389                         <td class="cell85">path describes the output directory. The
 390                         generated output is a registry file with the same name as the idl
 391                         input file.</td>
 392           </tr>
 393           <tr>
 394                     <td class="cell15"><code>-I&lt;path&gt;</code></td>
 395                         <td class="cell85">path specifies a directory where included files
 396                         that will be searched by the preprocessor are located. Multiple
 397                         directories can be combined with ';'.</td>
 398           </tr>
 399                   <tr>
 400             <td class="cell15"><code>-D&lt;name&gt;</code></td>
 401                         <td class="cell85">name defines a macro for the preprocessor.</td>
 402           </tr>
 403                   <tr>
 404             <td class="cell15"><code>-C</code></td>
 405                         <td class="cell85">generates complete type information, including
 406                         additional service information and documentation.</td>
 407           </tr>
 408                   <tr>
 409             <td class="cell15"><code>-h|?</code></td>
 410                         <td class="cell85">print this help message and exit.</td>
 411           </tr>
 412                   </table>
 413                   </p>
 414                   </td>
 415                 </tr>
 416       </table>
 417     </td>
 418     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 419   </tr>
 420   <tr>
 421     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 422   </tr>
 423   <tr>
 424     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 425     <td>
 426       <table class="table2">
 427         <tr>
 428                   <td colspan="2" class="head1"><a name="cppumaker"/>cppumaker</td>
 429                   <td align="right">
 430                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 431                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 432                   </td>
 433         </tr>
 434                 <tr>
 435                   <td colspan="3">
 436                   <p>The 'cppumaker' generates a C++ representation for idl types. The
 437                   cppumaker works on a typelibrary, which is generated by the UNOIDL
 438                   compiler (<a href="#idlc" link="link to the idlc tool description">
 439                   idlc</a>). It generates the output for all specified types and for all
 440                   types the specified types depend on.</p>
 441                   <p class="head2">Usage:</p>
 442                   <blockquote>
 443                   <b><code>cppumaker [-options] file_1 ... file_n</code></b>
 444                   </blockquote>
 445                   <p class="head2">Options:</p>
 446                   <p>
 447                   <table class="table4">
 448                   <tr>
 449             <td class="cell15"><code>-O&lt;path&gt;</code></td>
 450                         <td class="cell85">path describes the root directory for the
 451                         generated output. The output directory tree is generated under this
 452                         directory.</td>
 453           </tr>
 454                   <tr>
 455             <td class="cell15"><code>-T&lt;name&gt;<br>
 456                         |-T&lt;t1&gt;;&lt;t2&gt;...</code></td>
 457                         <td class="cell85">name specifies a type or a list of types. The
 458                         output for this type and all dependent types are generated. If no '-T'
 459                         option is specified, then output for all types is generated. It is also
 460                         possible to use a wildcard 'xy.*' to generate a complete module
 461                         inclusive all subdirectories. The use of '-T*' is equivalent to no '-T'
 462                         option. Example: 'com.sun.star.uno.XInterface' or
 463                         'com.sun.star.uno.*' are valid types.
 464                         </td>
 465           </tr>
 466                   <tr>
 467             <td class="cell15"><code>-B&lt;name&gt;</code></td>
 468                         <td class="cell85">name specifies the base node. All types are
 469                         searched under this node. Default is the root '/' of the registry
 470                         files.</td>
 471           </tr>
 472                   <tr>
 473             <td class="cell15"><code>-L</code></td>
 474                         <td class="cell85">UNO type functions are generated lightweight, that
 475                         means only the name and typeclass are given and everything else is
 476                         retrieved from the type library dynamically. The default is that UNO
 477                         type functions provides enough type information for boostrapping C++.
 478                         '-L' should be the default for external components.</td>
 479           </tr>
 480                   <tr>
 481             <td class="cell15"><code>-C</code></td>
 482                         <td class="cell85">UNO type functions are generated comprehensive
 483                         that means all necessary information is available for bridging the
 484                         type in UNO.
 485             </td>
 486           </tr>
 487                   <tr>
 488             <td class="cell15"><code>-G</code></td>
 489                         <td class="cell85">generate only target files which do not
 490                         exist.</td>
 491           </tr>
 492           <tr>
 493             <td class="cell15"><code>-Gc</code></td>
 494                         <td class="cell85">generate only target files whose content will
 495                         be changed.</td>
 496                   </tr>
 497                   <tr>
 498             <td class="cell15"><code>-X&lt;name&gt;</code></td>
 499                         <td class="cell85">extra types, which are not be taken into account
 500                         for generation.</td>
 501           </tr>
 502                   </table>
 503                   </p>
 504                   </td>
 505                 </tr>
 506       </table>
 507     </td>
 508     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 509   </tr>
 510   <tr>
 511     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 512   </tr>
 513   <tr>
 514     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 515     <td>
 516       <table class="table2">
 517         <tr>
 518                   <td colspan="2" class="head1"><a name="javamaker"/>javamaker</td>
 519                   <td align="right">
 520                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 521                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 522                   </td>
 523         </tr>
 524                 <tr>
 525                   <td colspan="3">
 526                   <p>The 'javamaker' generates the appropriate Java class file for each idl
 527                   type. The javamaker works on a typelibrary which is generated by the
 528                   UNOIDL compiler (<a href="#idlc" link="link to the idlc tool description">
 529                   idlc</a>). It generates the output for all specified types and for all
 530 types the specified types depend on.</p>
 531                   <p class="head2">Usage:</p>
 532                   <blockquote>
 533                   <b><code>javamaker [-options] file_1 ... file_n -Xfile_n+1 -Xfile_n+2</code></b>
 534                   </blockquote>
 535                   <p class="head2">Options:</p>
 536                   <p>
 537                   <table class="table4">
 538                   <tr>
 539             <td class="cell15"><code>-O&lt;path&gt;</code></td>
 540                         <td class="cell85">path describes the root directory for the
 541                         generated output. The output directory tree is generated under this
 542                         directory.</td>
 543           </tr>
 544                   <tr>
 545             <td class="cell15"><code>-T&lt;name&gt;|-T&lt;t1&gt;;&lt;t2&gt;...</code></td>
 546                         <td class="cell85">name specifies a type or a list of types. The
 547                         output for this type and all dependent types are generated. If no '-T'
 548                         option is specified, then output for all types is generated. It is also
 549                         possible to use a wildcard 'xy.*' to generate a complete module
 550                         inclusive all subdirectories. The use of '-T*' is equivalent to no '-T'
 551                         option. Example: 'com.sun.star.uno.XInterface'
 552                         or 'com.sun.star.uno.*' are valid types.
 553             </td>
 554           </tr>
 555                   <tr>
 556                     <td class="cell15"><code>-B&lt;name&gt;</code></td>
 557                         <td class="cell85">name specifies the base node. All types are
 558                         searched under this node. Default is the root '/' of the registry
 559                         files.</td>
 560           </tr>
 561           <tr>
 562             <td class="cell15"><code>-nD</code></td>
 563                         <td class="cell85">no dependent types are generated.</td>
 564           </tr>
 565                   <tr>
 566             <td class="cell15"><code>-G</code></td>
 567                         <td class="cell85">generate only target files which do not
 568                         exist.</td>
 569           </tr>
 570                   <tr>
 571             <td class="cell15"><code>-Gc</code></td>
 572                         <td class="cell85">generate only target files whose content will
 573                         be changed.</td>
 574           </tr>
 575           <tr>
 576             <td class="cell15"><code>-X&lt;name&gt;</code></td>
 577                         <td class="cell85">extra types, which will not be taken into account
 578                         for generation.</td>
 579           </tr>
 580                   </table>
 581                   </p>
 582                   </td>
 583                 </tr>
 584       </table>
 585     </td>
 586     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 587   </tr>
 588   <tr>
 589     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 590   </tr>
 591   <tr>
 592     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 593     <td>
 594       <table class="table2">
 595         <tr>
 596                   <td colspan="2" class="head1"><a name="climaker"/>climaker</td>
 597                   <td align="right">
 598                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 599                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 600                   </td>
 601         </tr>
 602                 <tr>
 603                   <td colspan="3">
 604                   <p>The 'climaker' (windows only) generates the appropriate CLI assemblies file for each idl
 605                   type. The climaker works on a typelibrary which is generated by the
 606                   UNOIDL compiler (<a href="#idlc" link="link to the idlc tool description">
 607                   idlc</a>). It generates the output for all specified types and for all
 608                     types the specified types depend on.</p>
 609                   <p class="head2">Usage:</p>
 610                   <blockquote>
 611                   <b><code>climaker &lt;switches&gt; [registry-file-1 registry-file-2 ...]</code></b>
 612                   </blockquote>
 613                   <p class="head2">Options:</p>
 614                   <p>
 615                   <table class="table4">
 616                   <tr>
 617                     <td class="cell15"><code>-O, --out &lt;output_file&gt;</code></td>
 618                     <td class="cell85">output assembly file;<br>
 619                       defaults to cli_unotypes.dll if more than one registry-file is given, else &lt;registry-file&gt;.dll</td>
 620                   </tr>
 621                   <tr>
 622                     <td class="cell15"><code>-T, --types &lt;type1[;type2;...]&gt;</code></td>
 623                     <td class="cell85">types to be generated (if none is given,
 624                       then all types of given registries are emitted</td>
 625                   </tr>
 626                   <tr>
 627                     <td class="cell15"><code>-X, --extra &lt;rdb-file&gt;></code></td>
 628                     <td class="cell85">additional rdb to saturate referenced types in
 629                       given registry file(s); these types will not be
 630                       emitted into the output assembly file</td>
 631                   </tr>
 632                   <tr>
 633                     <td class="cell15"><code>-r, --reference &lt;assembly-file&gt;</code></td>
 634                     <td class="cell85">reference metadata from assembly file</td>
 635                   </tr>
 636                   <tr>
 637                     <td class="cell15"><code>-k, --keyfile</code></td>
 638                     <td class="cell85">keyfile needed for strong name</td>
 639                   </tr>
 640                   <tr>
 641                     <td class="cell15"><code>--assembly-version &lt;version&gt;</code></td>
 642                     <td class="cell85">sets assembly version</td>
 643                   </tr>
 644                   <tr>
 645                     <td class="cell15"><code>--assembly-description &lt;text&gt;</code></td>
 646                     <td class="cell85">sets assembly description text</td>
 647                   </tr>
 648                   <tr>
 649                     <td class="cell15"><code>--assembly-product &lt;text&gt;</code></td>
 650                     <td class="cell85">sets assembly product name</td>
 651                   </tr>
 652                   <tr>
 653                     <td class="cell15"><code>--assembly-company &lt;text&gt;</code></td>
 654                     <td class="cell85">sets assembly company</td>
 655                   </tr>
 656                   <tr>
 657                     <td class="cell15"><code>--assembly-copyright &lt;text&gt;</code></td>
 658                     <td class="cell85">sets assembly copyright</td>
 659                   </tr>
 660                   <tr>
 661                     <td class="cell15"><code>--assembly-trademark &lt;text&gt;</code></td>
 662                     <td class="cell85">sets assembly trademark</td>
 663                   </tr>
 664                   <tr>
 665                     <td class="cell15"><code>-v, --verbose</code></td>
 666                     <td class="cell85">verbose output to stdout</td>
 667                   </tr>
 668                   <tr>
 669                     <td class="cell15"><code>-h, --help</code></td>
 670                     <td class="cell85">this message</td>
 671                   </tr>
 672
 673                   </table>
 674                   </p>
 675                   <p><b>Example:</b> <code>climaker --out cli_mytypes.dll --reference cli_uretypes.dll --extra types.rdb mytypes.rdb</code></p>
 676                   </td>
 677                 </tr>
 678       </table>
 679     </td>
 680     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 681   </tr>
 682   <tr>
 683     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 684   </tr>
 685   <tr>
 686     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 687     <td>
 688       <table class="table2">
 689         <tr>
 690                   <td colspan="2" class="head1"><a name="uno-skeletonmaker"/>uno-skeletonmaker</td>
 691                   <td align="right">
 692                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 693                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 694                   </td>
 695         </tr>
 696                 <tr>
 697                   <td colspan="3">
 698                   <p>The 'uno-skeletonmaker' is a tool to simplify the UNO component development. It has different modes, from simply dumping code definitions for different languages on stdout up to generating complete code skeletons. The generation of code skeletons support common component skeletons as well as specialized skeletons for special service provider interfaces.</p>
 699                   <p class="head2">Usage:</p>
 700                   <blockquote>
 701                   <b><code>
 702                         uno-skeletonmaker (-env:INIFILENAME=&lt;url&gt; | -env:UNO_TYPES=&lt;url>) dump [&lt;options>] -t &lt;type&gt; ...<br>
 703                         uno-skeletonmaker (-env:INIFILENAME=&lt;url&gt; | -env:UNO_TYPES=&lt;url&gt;) component [&lt;options&gt;] -n &lt;name&gt; -t &lt;type&gt; ...<br>
 704                         uno-skeletonmaker (-env:INIFILENAME=&lt;url&gt; | -env:UNO_TYPES=&lt;url&gt;) calc-add-in [&lt;options&gt;] -n &lt;name&gt; -t &lt;add-in_service&gt;<br>
 705                         uno-skeletonmaker (-env:INIFILENAME=&lt;url&gt; | -env:UNO_TYPES=&lt;url&gt;) add-on [&lt;options&gt;] -n &lt;name&gt; -p &lt;protocol_name:command,...&gt;
 706                         uno-skeletonmaker -V, --version<br>
 707                         uno-skeletonmaker -h, --help<br>
 708                   </code></b>
 709                   </blockquote>
 710                   <p class="head2">Sub-commands:</p>
 711                   <p>
 712                   <table class="table4">
 713                   <tr>
 714                     <td class="cell15"><code>dump</code></td>
 715                     <td class="cell85">dump declarations on stdout (e.g. constructors, methods, type mapping for properties) or complete method bodies with method forwarding.</td>
 716                   </tr>
 717                   <tr>
 718                     <td class="cell15"><code>component</code></td>
 719                     <td class="cell85">generates language specific code skeleton files using the implementation name as the file and class name</td>
 720                   </tr>
 721                   <tr>
 722                     <td class="cell15"><code>calc-add-in</code></td>
 723                     <td class="cell85">generates a language specific code skeleton for a Calc Add-Ins using the implementation name as the file and class name. A service type is necessary, referencing an interface which defines the new add-in functions.</td>
 724                   </tr>
 725                   <tr>
 726                     <td class="cell15"><code>add-on</code></td>
 727                     <td class="cell85">generates a language specific code skeleton for an add-on compnent using the implementation name as the file and class name. The protocol name(s) and the corresponding command(s) have to be specified with the '-p' option.</td>
 728                   </tr>
 729                   </table>
 730                   </p>
 731                   <p class="head2">Options:</p>
 732                   <p>
 733                   <table class="table4">
 734                   <tr>
 735             <td class="cell15"><code>-env:INIFILENAME=&lt;url&gt;</code></td>
 736                         <td class="cell85">url specifies a URL to an UNO ini|rc file of an existing UNO environment (URE, office installation).</td>
 737           </tr>
 738                   <tr>
 739             <td class="cell15"><code>-env:UNO_TYPES=&lt;url&gt;</code></td>
 740                         <td class="cell85">url specifies a binary type library file. It can be a space separated list of urls.</td>
 741           </tr>
 742                   <tr>
 743                     <td class="cell15"><code>-a, --all</code></td>
 744                         <td class="cell85">list all interface methods, not only the direct ones</td>
 745           </tr>
 746           <tr>
 747             <td class="cell15"><code>--(java4|java5|cpp)</code></td>
 748                         <td class="cell85">select the target language<br>
 749                         --java4 generate output for Java 1.4 or earlier<br>
 750                         --java5 generate output for Java 1.5 or later (is currently the default)<br>
 751                         --cpp generate output for C++</td>
 752           </tr>
 753                   <tr>
 754             <td class="cell15"><code>-sn, --shortnames</code></td>
 755                         <td class="cell85">using namespace abbreviation 'css:': for     '::com::sun::star::', only valid for sub-command 'dump' and target language 'cpp'. It is default for the sub-command 'component'.</td>
 756           </tr>
 757                   <tr>
 758             <td class="cell15"><code>--propertysetmixin</code></td>
 759                         <td class="cell85">the generated skeleton implements the cppu::PropertySetMixin helper if a referenced new style service specifies an interface which provides attributes (directly or inherited).</td>
 760           </tr>
 761           <tr>
 762             <td class="cell15"><code>-lh --licenseheader</code></td>
 763                         <td class="cell85">generates a default LibreOffice MPLv2 license header at the beginning of a component source file. This option is taken into account in 'component' mode only and if -o is unequal 'stdout'.</td>
 764           </tr>
 765           <tr>
 766             <td class="cell15"><code>-bc<br>--backward-compatible</code></td>
 767                         <td class="cell85">specifies that the generated calc add-in is backward compatible to older office versions and implement the former required add-in interfaces where the implementation is mapped on the new add-in configuration. In this case the config schema needs to be bundled with the extension add-in as well. Default is a minimal add-in component skeleton based on the add-in configuration coming with the office since OO.org 2.0.4.</td>
 768           </tr>
 769           <tr>
 770             <td class="cell15"><code>-o &lt;path&gt;</code></td>
 771                         <td class="cell85">path specifies an existing directory where the output files are generated to, only valid for sub-command 'component'. If path=stdout the generated code is generated on standard out instead of a file.</td>
 772           </tr>
 773           <tr>
 774             <td class="cell15"><code>-l &lt;file&gt;</code></td>
 775                         <td class="cell85">specifies a binary type library (can be used more than once). The type library is integrated as an additional type provider in the bootstrapped type system.</td>
 776           </tr>
 777           <tr>
 778             <td class="cell15"><code>-n &lt;name&gt;</code></td>
 779                         <td class="cell85">specifies an implementation name for the component (used as classname, filename and package|namespace name). In 'dump' mode it is used as classname (e.g. &quot;MyBase::&quot;, C++ only) to generate method bodies not inline.</td>
 780           </tr>
 781           <tr>
 782             <td class="cell15"><code>-d &lt;name&gt;</code></td>
 783                         <td class="cell85">specifies a base classname or a delegator. In 'dump' mode it is used as a delegator to forward methods. It can be used as '&lt;name&gt;::' for base forwarding, or '&lt;name&gt;-&gt;|.' for composition. Using &quot;_&quot; means that a default bodies with default return values are dumped.</td>
 784           </tr>
 785           <tr>
 786             <td class="cell15"><code>-t &lt;name&gt;</code></td>
 787                         <td class="cell85">specifies an UNOIDL type name, e.g. com.sun.star.text.XText (can be used more than once).</td>
 788           </tr>
 789           <tr>
 790             <td class="cell15"><code>-p &lt;protocol:cmd(s)&gt;</code></td>
 791                         <td class="cell85">specifies an add-on protocol name and the corresponding command names, where the commands are a ',' separated list of unique commands. This option is only valid for add-ons.</td>
 792           </tr>
 793           <tr>
 794             <td class="cell15"><code>-V, --version</code></td>
 795                         <td class="cell85">print version number and exit.</td>
 796           </tr>
 797           <tr>
 798             <td class="cell15"><code>-h, --help</code></td>
 799                         <td class="cell85">print this help and exit.</td>
 800           </tr>
 801                   </table>
 802                   </p>
 803                   </td>
 804                 </tr>
 805       </table>
 806     </td>
 807     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 808   </tr>
 809   <tr>
 810     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 811   </tr>
 812   <tr>
 813     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 814     <td>
 815       <table class="table2">
 816         <tr>
 817                   <td colspan="2" class="head1"><a name="regmerge"/>regmerge</td>
 818                   <td align="right">
 819                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 820                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 821                   </td>
 822         </tr>
 823                 <tr>
 824                   <td colspan="3">
 825                   <p>'regmerge' is a small tool to merge different registry files under a
 826                   specified key into another registry file. If a value already exists in
 827                   the target file the value is overwritten by the value of the source
 828                   file.</p>
 829                   <p class="head2">Usage:</p>
 830                   <blockquote>
 831                   <b><code>regmerge [-v|--verbose] &lt;mergefile&gt; &lt;mergeKeyName&gt; &lt;regfile_1&gt; ... &lt;regfile_n&gt;</code></b>
 832                   </blockquote>
 833                   <p class="head2">Options:</p>
 834                   <p>
 835                   <table class="table4">
 836                   <tr>
 837             <td class="cell15"><code>-v|--verbose</code></td>
 838                         <td class="cell85">verbose output on stdout.</td>
 839           </tr>
 840                   <tr>
 841             <td class="cell15"><code>&lt;mergefile&gt;</code></td>
 842                         <td class="cell85">specifies the merged registry file. If this file
 843                         doesn't exist, it is created.</td>
 844                   </tr>
 845                   <tr>
 846             <td class="cell15"><code>&lt;mergeKeyName&gt;</code></td>
 847                         <td class="cell85">specifies the merge key, everything is merged
 848                         under this key. If this key doesn't exist, it is created.</td>
 849           </tr>
 850                   <tr>
 851             <td class="cell15"><code>&lt;regfile_1&gt; ... &lt;regfile_n&gt;</code></td>
 852                         <td class="cell85">specifies one or more registry files that are
 853                         merged.</td>
 854                   </tr>
 855                   </table>
 856                   </p>
 857                   </td>
 858                 </tr>
 859       </table>
 860     </td>
 861     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 862   </tr>
 863   <tr>
 864     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 865   </tr>
 866   <tr>
 867     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 868     <td>
 869       <table class="table2">
 870         <tr>
 871                   <td colspan="2" class="head1"><a name="regview"/>regview</td>
 872                   <td align="right">
 873                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 874                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 875                   </td>
 876         </tr>
 877                 <tr>
 878                   <td colspan="3">
 879                   <p>'regview' is a tool to show the contents of a registry file. The tool
 880                   dumps the hierarchical structure and the values of the nodes in a human
 881                   readable manner to stdout.</p>
 882                   <p class="head2">Usage:</p>
 883                   <blockquote>
 884                   <b><code>regview &lt;registryfile&gt; [&lt;keyName&gt;]</code></b>
 885                   </blockquote>
 886                   <p class="head2">Options:</p>
 887                   <p>
 888                   <table class="table4">
 889                   <tr>
 890             <td class="cell15">-br&lt;registryfile&gt;</code></td>
 891                         <td class="cell85">the name of the registry whose contents should
 892                         be viewed.</td>
 893           </tr>
 894                   <tr>
 895             <td class="cell15"><code>&lt;keyName&gt;</code></td>
 896                         <td class="cell85">the name of a registry key. The name must be
 897                         fully qualified; for example, '/' means the root key and
 898                         '/UCR/com/sun/star/uno/XInterface' shows the type specification of the
 899                         XInterface type. If no key is specified, the tool dumps the whole
 900                         content of the registry file.</td>
 901                   </tr>
 902                   </table>
 903                   </p>
 904                   </td>
 905                 </tr>
 906       </table>
 907     </td>
 908     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 909   </tr>
 910   <tr>
 911     <td colspan="3"><img class="line" src="images/sdk_line-1.gif"></td>
 912   </tr>
 913   <tr>
 914     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
 915     <td>
 916       <table class="table2">
 917         <tr>
 918                   <td colspan="2" class="head1"><a name="autodoc"/>autodoc</td>
 919                   <td align="right">
 920                     <a href="#tools" title="link to the tools overview"><img class="navigate" src="images/nav_up.png"></a>
 921                     <a href="../index.html" title="link to the SDK start page"><img class="navigate" src="images/nav_home.png"></a>
 922                   </td>
 923         </tr>
 924                 <tr>
 925                   <td colspan="3">
 926                   <p>The 'autodoc' tool is used for creating javadoc-like documentation
 927                   from C++ and UNOIDL source code.</p>
 928                   <p>There are some conventions to follow when documenting C++- or
 929                   UNOIDL-sourcecode. See also the <a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/AppendixB/IDL_Documentation_Guidelines" title="link to the UNOIDL Documentation Guidelines">UNOIDL Documentation Guidelines</a>.<br>
 930           If you are not familiar with these, but do know javadoc: For simple C++
 931                   sourcecode documentation, using javadoc-style comments will work.</p>
 932                   <p class="head2">Usage:</p>
 933                   <blockquote>
 934                   <b><code>autodoc [ -v &lt;VerboseNr&gt; ] [ -name "&lt;TitleForTheDocu&gt;" ] -html &lt;OutputDirectory&gt; -lg &lt;SourcecodeLanguage&gt;<br>
 935           { [ -p &lt;ProjectName&gt; &lt;ProjectRootDirectory&gt; ] &nbsp;-t &lt;SourceTree&gt;* | -d &lt;SourceDirectory&gt;* | -f &lt;SourceFile&gt;* }*</code></b>
 936                   </blockquote>
 937                   <p class="head2">Options:</p>
 938                   <p>
 939                   <table width="100%" border="1" cellpadding="4" cellspacing="0">
 940                   <tr>
 941             <td class="cell15"><code>-v &lt;VerboseNr&gt;</code></td>
 942             <td class="cell85">&lt;VerboseNr&gt; == 5 displays the parsed source
 943                     code tokens, so you can locate which piece caused an parsing error.<br>
 944             &lt;VerboseNr&gt; == 2 displays not only the parsed source code,
 945                     but also the comments.<br><br>
 946                     This option must be the first one, if it is used.</td>
 947           </tr>
 948           <tr>
 949             <td class="cell15"><code>-name "&lt;Title&gt;"</code></td>
 950                     <td class="cell85">&lt;Title&gt; occurs as the title of the start
 951                     page of the HTML output. If this option is omitted, a default title is
 952                     created.</td>
 953           </tr>
 954           <tr>
 955             <td class="cell15"><code>-html &lt;OutputDirectory&gt;</code></td>
 956             <td class="cell85">specifies the root directory where the HTML output
 957                     is created.<br>
 958             Autodoc does not remove old files there, though it overwrites them.</td>
 959           </tr>
 960           <tr>
 961             <td class="cell15"><code>-lg &lt;SourcecodeLanguage&gt;</code></td>
 962                     <td class="cell85">Possible values are: c++ | idl.<br><br>
 963             This also specifies which files will be parsed: &quot;c++&quot; parses
 964                         all files with the endings .hxx and .h, &quot;idl&quot; parses all
 965                         files with the ending '.idl' .<br>
 966             To change this behaviour, see at option <code>-f</code>.</td>
 967           </tr>
 968                   <tr>
 969             <td class="cell15"><code>-p &lt;ProjectName&gt; &lt;ProjectDirectory&gt;</code></td>
 970                     <td class="cell85">this option can be used to divide large code
 971                     bases into different projects.<br>
 972             &lt;ProjectName&gt; gives a user-defined name for the project.<br>
 973             &lt;ProjectDirectory&gt; is the root to which all paths, given with the
 974                     following options <code>-t,-d</code> and <code>-f</code>, are
 975                         relative.<br>
 976                     This option can be omitted when there are no projects and all paths in
 977                     the following options are relative to the working directory.<br><br>
 978                     The &quot;{ ... }*&quot; around the options <code>-p,-t,-d,-f</code>
 979                         indicates, that this whole block of options can be repeated, each block
 980                         starting with a new <code>-p</code>.</td>
 981           </tr>
 982           <tr>
 983             <td class="cell15"><code>-t &lt;SourceTree&gt;</code></td>
 984                     <td class="cell85">specifies that all files in the directory
 985                     &lt;SourceTree&gt; and it's subdirectories are parsed, where the file
 986                     ending matches the option <code>-lg</code>.<br>
 987             There can be given multiple directories after one <code>-t</code>
 988                         option.<br>
 989             All relative paths &nbsp;are relative to the project-rootdirectory,
 990                     given with the <code>-p</code> option.<br>
 991             </td>
 992           </tr>
 993           <tr>
 994                     <td class="cell15"><code>-d &lt;SourceDirectory&gt;</code></td>
 995             <td class="cell85">Specifies that all files in th directory
 996                     &lt;SourceDirectory&gt;, but NOT it's subdirectories, are parsed, where
 997                     the file ending matches the option <code>-lg</code>.<br>
 998             There can be multiple directories given after one <code>-d</code>
 999                         option.<br>
1000             All relative paths &nbsp;are relative to the project-rootdirectory,
1001                         given with the <code>-p</code> option.</td>
1002           </tr>
1003           <tr>
1004             <td class="cell15"><code>-f &lt;SourceFile&gt;</code></td>
1005             <td class="cell85">parses the given file. The ending does not have
1006                     to match the <code>-lg</code> option.<br>
1007             There can be multiple files given after one <code>-f</code> option.<br>
1008             All relative paths &nbsp;are relative to the project-rootdirectory,
1009                     given with the <code>-p</code> option.</td>
1010           </tr>
1011                   </table>
1012                   </p><b>Remark:</b> The sequence of options matters! Use them in the order given
1013                   in the &quot;Usage&quot;-paragraph.</p>
1014                   </td>
1015                 </tr>
1016       </table>
1017     </td>
1018     <td class="content1"><img class="nothing8" src="images/nada.gif"></td>
1019   </tr>
1020 </table>
1021                 </div>
1022                 <div id="Footer">
1023                     <div id="FooterText">
1024                         <p>
1025                             Copyright © 2000, 2013 LibreOffice contributors and/or their affiliates. All rights reserved.
1026                             <br>
1027                             LibreOffice was created by The Document Foundation,
1028                             based on Apache OpenOffice, which is Copyright 2011
1029                             The Apache Software Foundation.
1030                             <br>
1031                             The Document Foundation acknowledges all community members, please find more info <a href="http://www.libreoffice.org/about-us/credits/" target="_blank">at our website</a>.
1032                         </p>
1033                         <p>
1034                             &nbsp;
1035                         </p>
1036                         <p>
1037                             <a href="http://www.documentfoundation.org/privacy" target="_blank">Privacy Policy</a> | <a href="http://www.documentfoundation.org/imprint" target="_blank">Impressum (Legal Info)</a>
1038                             | Copyright information: The source code of LibreOffice is licensed under the GNU Lesser General Public License (<a href="http://www.libreoffice.org/download/license/" target="_blank">LGPLv3</a>). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our <a href="http://wiki.documentfoundation.org/TradeMark_Policy" target="_blank">trademark policy</a>.
1039                         </p>
1040                     </div>
1041                 </div>
1042             </div>
1043         </div>
1044     </body>
1045 </html>
1046