incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1175537 [2/3] - /incubator/ooo/ooo-site/trunk/content/tools/
Date Sun, 25 Sep 2011 19:39:09 GMT
Added: incubator/ooo/ooo-site/trunk/content/tools/build_env_modstruct.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/tools/build_env_modstruct.html?rev=1175537&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/tools/build_env_modstruct.html (added)
+++ incubator/ooo/ooo-site/trunk/content/tools/build_env_modstruct.html Sun Sep 25 19:39:08 2011
@@ -0,0 +1,368 @@
+<html>
+<head>
+<title>OpenOffice.org - CVS Module Structure</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<H2>CVS Module Structure</H2>
+
+<P>
+The following sections describe the general file structure of modules.
+</P>
+
+<UL>
+<LI>
+<A HREF="build_env_modstruct.html#3.4.1.TopLevelCVSModuleDirectoryStructure|outline">Top Level
+CVS Module Directory Structure</A></LI>
+
+<LI>
+<A HREF="build_env_modstruct.html#3.4.2.CompiledObjectsor$INPATHDirectoryStructure|outline">Compiled
+Objects or $INPATH Directory Structure</A></LI>
+</ul>
+
+
+<H3>
+<a NAME="3.4.1.TopLevelCVSModuleDirectoryStructure|outline"></A>Top Level
+Module Directory Structure</H3>
+
+<P>
+The following table lists the subdirectories of a typical module directory,
+and describes the contents of those subdirectories. You can also view an
+<A HREF="modules.gif">illustration</A> of the module directory
+structure.
+</P>
+
+<table BORDER=0 CELLSPACING=0 CELLPADDING=0 >
+<tr VALIGN=TOP>
+<TH>Directory</TH>
+
+<TH>Description</TH>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR>
+</TD>
+
+<TD>The root directory of the module.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/inc</CODE>
+</TD>
+
+<TD>Contains the header files and interface descriptions for the module.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/prj</CODE>
+</TD>
+
+<TD>Contains the file <CODE>d.lst</CODE>. This file lists all the deliverables
+of the module. It details where the deliverables come from and where they
+go to.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/source</CODE>
+</TD>
+
+<TD>Contains source files and a makefile to compile the source.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/util</CODE>
+</TD>
+
+<TD>Linking to binaries occurs here. This directory contains a makefile
+that specifies how to build the module libraries or binaries.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/$INPATH</CODE>
+</TD>
+
+<TD>The name of this directory comes from the <CODE>INPATH</CODE> variable.
+The <CODE>INPATH</CODE> variable derives from the <CODE>OUTPATH</CODE> and <CODE>PROEXT</CODE>
+variables. For example, a directory called <VAR>module-name</VAR>/<CODE>unxlngi3.pro</CODE> 
+may exist or will be created when starting to build this platform.
+<P>All compiled objects, libraries, and binaries are built into this directory.
+From there they are delivered to <CODE>solver</CODE>. For more information
+on this directory, see 
+<a href="3.4.2.CompiledObjectsor$INPATHDirectoryStructure|outline">Compiled
+Objects or $INPATH Directory Structure</A>.</P></TD>
+
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/common.pro</CODE>
+</TD>
+
+<TD>Contains platform-independent output, such as resource files, <CODE>.jar</CODE>
+files, and <CODE>.zip</CODE> files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/res</CODE>
+</TD>
+
+<TD>Contains typical resource files such as bitmaps, icons, and cursor
+files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/sdi</CODE>
+</TD>
+
+<TD>Contains View Definition Interface files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/unoidl</CODE>
+</TD>
+
+<TD>Contains the UNO IDL compiler for <CODE>.idl</CODE> files, supplied with
+backends for C++, Java, documentation, and so on.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/workben</CODE>
+</TD>
+
+<TD>Contains test applications.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+</TD>
+
+<TD></TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/mac</CODE>
+</TD>
+
+<TD>Contains implementation files specific to Macintosh.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/os2</CODE>
+</TD>
+
+<TD>Contains implementation files specific to OS/2.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/unx</CODE>
+</TD>
+
+<TD>Contains implementation files specific to X Windows System.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<VAR>module-name</VAR><CODE>/win</CODE>
+</TD>
+
+<TD>Contains implementation files specific to Win32.</TD>
+</TR>
+</table>
+
+<H3>
+<a NAME="3.4.2.CompiledObjectsor$INPATHDirectoryStructure|outline"></A>Compiled
+Objects or $INPATH Directory Structure</H3>
+
+<P>
+The following table lists the subdirectories of a typical output directory, 
+and describes the contents of those subdirectories.
+</P>
+
+<table BORDER=0 CELLSPACING=0 CELLPADDING=0 >
+
+<tr VALIGN=TOP>
+<TH>Directory</TH>
+
+<TH>Description</TH>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>$INPATH</CODE>
+</TD>
+
+<TD>Root directory of the output structure.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>bin</CODE>
+</TD>
+
+<TD>Contains binary and files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>class</CODE>
+</TD>
+
+<TD>Contains Java-compiled class and/or jar files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>dbo</CODE>
+</TD>
+
+<TD>In the past, this directory contained debug information from the Writer
+project only. It is obsolete now.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>dib</CODE>
+</TD>
+
+<TD></TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>dlb</CODE>
+</TD>
+
+<TD>In the past, this directory contained debug information from the Writer
+project only. It is obsolete now.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>doc</CODE>
+</TD>
+
+<TD>Contains generated HTML.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>dso</CODE>
+</TD>
+
+<TD>In the past, this directory contained debug information from the Writer
+project only. It is obsolete now.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>idl</CODE>
+</TD>
+
+<TD>Contains Interface definition Language (IDL) files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>inc</CODE>
+</TD>
+
+<TD>Contains project interface header files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>lib</CODE>
+</TD>
+
+<TD>Can contain the following files:
+<UL>
+<LI><CODE>.a</CODE> - Contains static UNIX libraries.</LI>
+<LI><CODE>.so</CODE> - Contains shared UNIX libraries.</LI>
+<LI><CODE>.lib</CODE> - On UNIX systems, contains a list of object files. 
+On Win32 systems, contains a collection of object files.</LI>
+<LI><CODE>.dump</CODE> - Contains the symbols within a library.</LI>
+</UL>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>misc</CODE>
+</TD>
+
+<TD>Contains a record of some of the commands run by the make process.
+This also contains the generated dependency description for this module.
+Typically, tools such as <CODE>makedep</CODE>, <CODE>javadep</CODE>, or <CODE>rscdep</CODE>
+generate this description. 
+Also contains generated Java files, in a <CODE>java</CODE> subdirectory.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>obj</CODE>
+</TD>
+
+<TD>Contains object files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>res</CODE>
+</TD>
+
+<TD>Contains resource files. These are organized in subdirectories named
+according to language codes. There are bitmaps in these subdirectories.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>slb</CODE>
+</TD>
+
+<TD>
+Contains <CODE>.lib</CODE> files. These list the objects to be compiled into a 
+shared library. On Win32 systems, the <CODE>.lib</CODE> files are a collection of objects.
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>slo</CODE>
+</TD>
+
+<TD>The shared library object (<CODE>slo</CODE>) directory contains object
+files that appear in shared libraries. Objects that appear in shared libraries
+appear in both the <CODE>obj</CODE> and <CODE>slo</CODE> directories.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>srs</CODE>
+</TD>
+
+<TD>Contains string resource files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>www</CODE>
+</TD>
+
+<TD>Contains files published on the internet.</TD>
+</TR>
+</table>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/tools/build_env_modstruct.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/tools/build_env_param.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/tools/build_env_param.html?rev=1175537&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/tools/build_env_param.html (added)
+++ incubator/ooo/ooo-site/trunk/content/tools/build_env_param.html Sun Sep 25 19:39:08 2011
@@ -0,0 +1,1125 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+<title>OpenOffice.org - Build Environment parameters</title>
+</head>
+<body>
+<H2>Build Environment Parameters</H2>
+<P>
+The following build environment parameters are in alphabetical order and
+not as as they appear in the file that is generated by the
+<CODE>configure</CODE>
+process. The name of this file depends on the system on which it was generated.
+</P>
+<P>
+Please note the following:
+</P>
+<ul TYPE=DISC>
+<LI>The term <EM>set</EM> means that an environment parameter is set to any
+value.</LI>
+
+<LI>The term <EM>not set</EM> means that an environment parameter is blank.</LI>
+
+<LI>For historical reasons the only exception from this rule is the 
+variable <CODE>UPDATER</CODE>, which is either set to <CODE>YES</CODE>, or 
+is not set.</LI>
+</ul>
+
+<P>
+The following table lists the environment parameters, and a description
+of each parameter. This information is based on the output of the <CODE>configure</CODE>
+process for the Linux, Solaris, Windows NT, and Mac OS X environments.
+</P>
+
+
+<table BORDER=0 CELLSPACING=0 CELLPADDING=5>
+
+<tr VALIGN=TOP>
+<TH>Build Environment Parameter</TH>
+
+<TH>Description</TH>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>BIG_GOODIES</CODE>
+</TD>
+
+<TD>If set, the build process only builds <CODE>libgo<VAR>xxx</VAR></CODE>, where
+<VAR>xxx</VAR> signifies the build number.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>BIG_SVX</CODE>
+</TD>
+
+<TD>If set, builds the shared libraries or dynamic link libraries as one
+library. Using one library may improve performance but this increases the
+link time significantly.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>BMP_WRITES_FLAG</CODE>
+</TD>
+
+<TD>
+Specifies whether the <CODE>bmp</CODE> tool writes a success message to a file when 
+the bitmap compiler runs successfully, or whether to use an <CODE>echo</CODE> command in the makefiles 
+to write this message. If set, <CODE>bmp</CODE> writes the message to a 
+<CODE>.don</CODE> file. By default, this parameter is set.
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>BOTH</CODE>
+</TD>
+
+<TD>
+If set, links shared libraries (DLLs) in both debug and non-debug
+modes on Win32-based platforms. The shared libraries in debug mode are
+built with an underscore (_) prefix.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>CLASSPATH</CODE>
+</TD>
+
+<TD>This variable is supported by the JDK and JRE. This variable defaults
+to the location of the JDK-supported standard <CODE>classes.zip</CODE> file.
+This variable is used by the JRE to locate this file or other class files
+used by the application. The <CODE>classes.zip</CODE> file is for JDK 1.1 versions
+only. This was replaced by <CODE>rt.jar</CODE> runtime jar files for Java SDK
+1.2 and higher.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>common_build</CODE>
+</TD>
+
+<TD>If set, creates platform independent output, such as resource files,
+jar files, and zip files. By default, this parameter is set.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>COMMON_BUILD_TOOLS</CODE>
+</TD>
+
+<TD>Used in the <CODE>officecfg</CODE> module. Contains the directory location of the
+JAXP-compliant XML parser <CODE>jar</CODE> files. By default, the value of
+this parameter is <CODE>$SRC_ROOT/external/common</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>COMMON_OUTDIR</CODE>
+</TD>
+
+<TD>
+Specifies where to place common files if <CODE>common_build</CODE> is set. 
+By default, the value of this parameter is <CODE>COMMON</CODE>. 
+No other value is required.
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>COM</CODE>
+</TD>
+
+<TD>Specifies the compiler to use in the build process, for example <CODE>gcc</CODE>
+on Linux and Mac OS X, <CODE>C50</CODE> on Solaris, or <CODE>MSC</CODE> on Win32.
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>COMEX</CODE>
+</TD>
+
+<TD>Specifies the compiler extension value.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>COMPATH</CODE>
+</TD>
+
+<TD>Specifies the location of the compiler.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>COMP_ENV</CODE>
+</TD>
+
+<TD>This parameter is used on Win32.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>CPU</CODE>
+</TD>
+
+<TD>The initial of the CPU name, for example:
+<ul TYPE=DISC>
+<LI><CODE>I</CODE> for Intel</LI>
+<LI><CODE>S</CODE> for Solaris SPARC</LI>
+<LI><CODE>P</CODE> for PowerPC</LI>
+<LI><CODE>R</CODE> for other RISC architectures</LI>
+</ul>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>CPUNAME</CODE>
+</TD>
+
+<TD>Full name of the CPU value in uppercase, for example:
+<ul TYPE=DISC>
+<LI><CODE>INTEL</CODE></LI>
+<LI><CODE>SPARC</CODE></LI>
+<LI><CODE>POWERPC</CODE></LI>
+</ul>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>CVER</CODE>
+</TD>
+
+<TD>The compiler version, for example:
+<ul TYPE=DISC>
+<LI><CODE>C300</CODE> for gcc version 3.0 or better</LI>
+<LI><CODE>C50</CODE> on Solaris</LI>
+<LI><CODE>C62</CODE> on Tru64</LI>
+<LI><CODE>C730</CODE> on Irix when using SGI MIPS compiler</LI>
+<LI><CODE>M1200</CODE> on Win32</LI>
+</ul>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>CVSROOT</CODE>
+</TD>
+
+<TD>CVS is a code version control system. The <CODE>CVSROOT</CODE> defines
+the server location of the CVS tree.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>deliver</CODE>
+</TD>
+
+<TD>If this parameter is set, <CODE>dmake</CODE> automatically delivers the
+project deliverables to the <CODE>solver</CODE> tree.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>DLLSUFFIX</CODE>
+</TD>
+
+<TD>Identifies the platform that you build on. This parameter can have
+values such as:
+<ul TYPE=DISC>
+<LI><CODE>li</CODE> for Linux, for example <CODE>libsw568li.so</CODE></LI>
+<LI><CODE>ss</CODE> for Solaris for example <CODE>libsw568ss.so</CODE></LI>
+<LI><CODE>mi</CODE> for Win32, for example <CODE>libsw568mi.dll</CODE></LI>
+<LI><CODE>mxp</CODE> for Mac OS X, for example <CODE>libsw568mxp.dylib</CODE></LI>
+</ul>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>DMAKEROOT</CODE>
+</TD>
+
+<TD>This parameter is set to the <CODE>$SRC_ROOT/solenv/inc/startup</CODE>
+directory.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>DYLD_LIBRARY_PATH</CODE>
+</TD>
+<TD>The directory locations used on Mac OS X to locate the runtime shared libraries.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>DYNAMIC_CRT</CODE>
+</TD>
+
+<TD>
+If this parameter is set, the build process uses the dynamic version of the C runtime 
+libraries, rather than the static version. This implies a compiler define and a 
+different set of libraries used for linking.
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>FRAMEWORKSHOME</CODE>
+</TD>
+
+<TD>
+Used on Mac OS X only. This is set to the location of the standard system frameworks, 
+for example, System.framework, AppKit.framework, and so on.
+</TD>
+</TR>
+
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>ENABLEUNICODE</CODE>
+</TD>
+
+<TD>If set, uses the UNICODE character set. It is implemented as a compile
+line parameter, and is implemented as <CODE>#ifdef</CODE> in code. By default,
+this parameter is set.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>give_me_all_languages</CODE>
+</TD>
+
+<TD>If set, the build process builds all resource libraries supported by
+the build environment. By default, this parameter is not set.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>GLIBC</CODE>
+</TD>
+
+<TD>Identifies the distribution version of Linux. This enables the build
+process to identify the location of the GNU C library.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>GUI</CODE>
+</TD>
+
+<TD>Specifies the category of operating system that you are building on.
+This parameter is set to values such as:
+<ul TYPE=DISC>
+<LI>
+<CODE>UNX</CODE> on Linux, Solaris, and Mac OS X</LI>
+
+<LI>
+<CODE>WNT</CODE> on Win32</LI>
+</ul>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>GUIBASE</CODE>
+</TD>
+
+<TD>This parameter is set to the following values:
+<ul TYPE=DISC>
+<LI><CODE>unx</CODE> on Linux</LI>
+<LI><CODE>unx</CODE> on Solaris</LI>
+<LI><CODE>WIN</CODE> on Win32</LI>
+<LI><CODE>unx</CODE> or <CODE>aqua</CODE> on Mac OS X</LI>
+</ul>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>IENV</CODE>
+</TD>
+
+<TD>This parameter is obsolete, and is replaced by <CODE>SOLARINC</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>ILIB</CODE>
+</TD>
+
+<TD>
+Makefiles use the <CODE>ILIB</CODE> parameter to set the value of <CODE>LIB</CODE>.
+This is used on Win32 operating systems only. The <CODE>LIB</CODE> parameter
+specifies the location where the Microsoft linker gets libraries from.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>INCLUDE</CODE>
+</TD>
+
+<TD>An internal <CODE>dmake</CODE> variable that indicates the include path
+search directories used by the compiler. For example, in <CODE>target.mk</CODE>
+the <CODE>INCLUDE</CODE> internal <CODE>dmake</CODE> variable contains the environment
+variable <CODE>SOLARINC</CODE>, some default locations in the source tree such
+as <VAR>module-name</VAR><CODE>/inc</CODE>, and the <CODE>inc</CODE> directory of
+the output tree.
+<P>This parameter is now obsolete, there is no need to change the values
+here.
+</P></TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>INPATH</CODE>
+</TD>
+
+<TD>The location of the delivered input path.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>JAVAHOME</CODE>
+</TD>
+
+<TD>This parameter is set on Win32 platforms to the location of the JDK,
+for example <CODE>N:\jdk118</CODE>. <CODE>JAVAHOME</CODE> is only set in the Win32
+environment.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>LD_LIBRARY_PATH</CODE>
+</TD>
+
+<TD>The directory locations used on Linux and Solaris to locate the runtime
+shared libraries.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>LIB</CODE>
+</TD>
+
+<TD>Specifies the location where the Microsoft linker gets links from.
+This parameter is set to the same value as <CODE>ILIB</CODE>. This is used
+on Win32 operating systems only.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>mk_tmp</CODE>
+</TD>
+
+<TD>If set, the <CODE>build</CODE> tool builds the directories in <CODE>solar$UPD.lst</CODE>,
+and ignores the subdirectories specified in the makefiles. If you use the
+<CODE>build</CODE> tool, it may set the <CODE>mk_tmp</CODE> variable. This can
+cause the following error while running <CODE>dmake</CODE>:
+
+<PRE>
+IGNORE SUBDIRS
+</PRE>
+
+<P>For <CODE>dmake</CODE> to run correctly, you must reset the value of <CODE>mk_tmp</CODE>,
+as follows in csh shells:</P>
+
+<PRE>
+% <KBD>unsetenv mk_tmp</KBD>
+</PRE>
+
+<P>Alternatively, on Win32 systems or bourne sh (eg bash), use the following command:</P>
+
+<PRE>
+C:\> <KBD>unset mk_tmp</KBD>
+</PRE>
+
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>MK_UNROLL</CODE>
+</TD>
+
+<TD>If set, the <CODE>target.mk</CODE> file includes <CODE>.mk</CODE> files preceded
+with an underscore (_). The files preceded with an underscore are an expanded version 
+of the makefiles. The following IF statement appears in the <CODE>target.mk</CODE>
+file:
+
+<PRE>
+IF "$(MK_UNROLL)"!=""
+.INCLUDE : _tg_def.mk
+.ELSE
+.INCLUDE : tg_def.mk
+.ENDIF
+</PRE>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>MULTITHREAD_OBJ</CODE>
+</TD>
+
+<TD>
+Builds multithreaded static objects (that is, files in 
+<CODE>$(OUT)$/obj</CODE>) when set. 
+This parameter is accessed in the <CODE>sal</CODE> and <CODE>osl</CODE> source makefiles. 
+By default, this parameter is set. 
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>NO_REC_RES</CODE>
+</TD>
+
+<TD>
+If set, specifies all language-dependent files not to build resources
+recursively. When <CODE>NO_REC_RES</CODE> is set, the build process does not
+use <CODE>solarlang</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>NOSOLAR_JAVA</CODE>
+</TD>
+
+<TD>This variable is obsolete. Use the <CODE>SOLAR_JAVA</CODE> build environment
+variable instead.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>OS</CODE>
+</TD>
+
+<TD>Specifies the operating system.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>OUTPATH</CODE>
+</TD>
+
+<TD>
+Specifies the basename of the output tree created during the build. Typical values for this 
+parameter are as follows:
+<ul TYPE=DISC>
+<LI>
+<CODE>unxlngi3</CODE> or <CODE>unxlngi4</CODE> for Linux on Intel with
+<CODE>gcc</CODE> compiler. This name uses the values of the
+<CODE>GUIBASE</CODE>, <CODE>OS</CODE>, and <CODE>COM</CODE>
+variables.</LI>
+
+<LI><CODE>unxsols2</CODE> for Solaris on SPARC.</LI>
+
+<LI><CODE>wntmsci3</CODE> for Win32 on Intel, with Microsoft Compiler.</LI>
+
+<LI><CODE>unxmacxp</CODE> for Mac OS X.</LI> 
+</ul>
+
+<P>
+The number at the end is used to identify the build environment.
+</P>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>PATH</CODE>
+</TD>
+
+<TD>The path environment variable.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>PATH_SEPARATOR</CODE>
+</TD>
+
+<TD>Separator character used in <CODE>$PATH</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>PERL</CODE>
+</TD>
+
+<TD>Set to the location of the Perl executable file, in Win32.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>PROEXT</CODE>
+</TD>
+
+<TD>Specifies the extension that is appended to <CODE>OUTPATH</CODE> to create
+the name of the output tree. A typical value for this parameter is <CODE>.pro</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>PROFULLSWITCH</CODE>
+</TD>
+
+<TD>Specifies to the <CODE>dmake</CODE> and <CODE>build</CODE> tools to build a
+product version of StarOffice or OpenOffice.org. This also passes the value of
+<CODE>PROSWITCH</CODE>
+to the compiler. This is implemented using aliases.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>PROSWITCH</CODE>
+</TD>
+
+<TD>Sets all debugging macros to empty. </TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_ARAB</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Arabic.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_CHINSIM</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Chinese Simplified.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_CHINTRAD</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Chinese Traditional.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_DAN</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Danish.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_DTCH</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Dutch.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_ENUS</CODE>
+</TD>
+
+<TD>Specifies to create resource files for US English. By default, this
+parameter is set.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_FREN</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for French.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_GREEK</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Greek.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_ITAL</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Italian.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_JAPN</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Japanese.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_KOREAN</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Korean.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_POL</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Polish.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_PORT</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Portuguese.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_RUSS</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Russian.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_SPAN</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Spanish.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_SWED</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Swedish.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RES_TURK</CODE>
+</TD>
+
+<TD>If this parameter is set, the build process creates resource files
+for Turkish.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>RSCRES</CODE>
+</TD>
+
+<TD>Specifies the location of the resource files. This is one of the ways
+to find binary resources for the <CODE>rsc</CODE> compiler. This is set to
+the value of the <CODE>$SRC_ROOT</CODE> variable.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SHELL</CODE>
+</TD>
+
+<TD>Points to the location of the shell binary, for example <CODE>csh</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SO3</CODE>
+</TD>
+
+<TD>Specifies to add the compile flag option <CODE>-DSO3</CODE> to the compiler.
+The <CODE>so3</CODE> module contains the base of the objects and also a bridge
+into the Microsoft OLE objects. By default, this parameter is set.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLAR_JAVA</CODE>
+</TD>
+
+<TD>Specifies whether JDK supports Solaris. This parameter is for Solaris
+only. By default, this parameter is set. This variable replaces the <CODE>NOSOLAR_JAVA</CODE>
+environment variable, which is now obsolete.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLAR_PLUGIN</CODE>
+</TD>
+
+<TD>Adds the <CODE>-DSOLAR_PLUGIN</CODE> to both the <CODE>CDEFS</CODE> and <CODE>RCSDEFS</CODE>
+compile options. By default, this parameter is set.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLAR_UPD</CODE>
+</TD>
+
+<TD>This is the same value as <CODE>$UPD</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARDEF</CODE>
+</TD>
+
+<TD>Specifies the compiler defines used on Linux and Solaris.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARENV</CODE>
+</TD>
+
+<TD>This parameter is set to the following value: <CODE>$SRC_ROOT/solenv</CODE></TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARENVINC</CODE>
+</TD>
+
+<TD>This is the same value as <CODE>$SOLARENV/inc</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLAREXTRALIB</CODE>
+</TD>
+
+<TD>Specifies by platform the locations used by the linker to locate libraries.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARINC</CODE>
+</TD>
+
+<TD>Specifies the location of the compiler include search directory paths.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARINCLUDES</CODE>
+</TD>
+
+<TD>Specifies the location of the compiler include search directory paths,
+only used on Win32. It includes the Microsoft Visual C include directories.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARLIB</CODE>
+</TD>
+
+<TD>Specifies the location of the linker library search directory paths.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARROOT</CODE>
+</TD>
+
+<TD>Set to the following value: <CODE>$SRC_ROOT</CODE></TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARSRC</CODE>
+</TD>
+
+<TD>Specifies the directory location of the projects directory.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARVER</CODE>
+</TD>
+
+<TD>Set to the following value: <CODE>$SRC_ROOT/solver</CODE></TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SOLARVERSION</CODE>
+</TD>
+
+<TD>Specifies the root of the output tree. This parameter is set to the
+same value as <CODE>SOLARVER</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SRC_ROOT</CODE>
+</TD>
+
+<TD>Specifies the top-level directory of the OpenOffice.org CVS tree.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>SSX_PATH</CODE>
+</TD>
+
+<TD>Includes the default path on the development machine, so that after
+you run the <CODE>setsolar</CODE> tool with different parameters, this contains
+the original path.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>STAR_INIROOT</CODE>
+</TD>
+
+<TD>This is the same value as <CODE>$SOLARENV/config</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>STAR_INIROOTOLD</CODE>
+</TD>
+
+<TD>This is the same value as <CODE>$SOLARENV/config</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>STAR_REGISTRY</CODE>
+</TD>
+
+<TD>Specifies the location of the registry database <CODE>applicat.rdb</CODE>.
+This is built in the <CODE>api</CODE> module.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>STAR_RESOURCEPATH</CODE>
+</TD>
+
+<TD>Specifies the location of the delivered resource files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>STAR_STANDLST</CODE>
+</TD>
+
+<TD>This is the same value as <CODE>$SOLARENV/config/stand.lst</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>STAR_SSCOMON</CODE>
+</TD>
+
+<TD>This is the same value as <CODE>$SOLARENV/config/ssolar.cmn</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>STAR_SSOLARINI</CODE>
+</TD>
+
+<TD>This is the same value as <CODE>$SOLARENV/config/ssolar.ini</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>TEMP</CODE>
+</TD>
+
+<TD>This parameter is set to <CODE>/tmp</CODE> on Linux and Solaris, and should
+be set to an existing directory on Win32, usually <CODE>C:\temp</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>TF_XXX</CODE>
+</TD>
+
+<TD>The build process uses this parameter for parallel integration of new
+features into the current build. This allows developers to introduce new
+features and set additional macros. If this feature then becomes accepted
+into the build then all references to it are deleted after a period of
+time.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>TF_PACKAGES</CODE>
+</TD>
+
+<TD>This parameter defaults to the <CODE>WORK_STAMP</CODE>, for example SRC569.
+If set this adds the <CODE>TF_ONE51</CODE> to the <CODE>CDEFS</CODE>, <CODE>UNOIDLDEFS</CODE>,
+and so on.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>TF_UCB</CODE>
+</TD>
+
+<TD>This parameter is set for Win32.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>TF_ONE51</CODE>
+</TD>
+
+<TD>This parameter defaults to the <CODE>WORK_STAMP</CODE>, for example SRC569.
+If set this adds the <CODE>TF_ONE51</CODE> to the <CODE>CDEFS</CODE>, <CODE>UNOIDLDEFS</CODE>,
+and so on.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>TF_SDBAPI</CODE>
+</TD>
+
+<TD>This parameter is set.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>TMP</CODE>
+</TD>
+
+<TD>This parameter is set to <CODE>/tmp</CODE> on Linux and Solaris. On Win32,
+set this to an existing directory. You must set both the <CODE>TMP</CODE>
+and <CODE>TEMP</CODE> parameters. They point to the same location.
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>UPD</CODE>
+</TD>
+
+<TD>This parameter is set to the current release build identifier.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>UPDATER</CODE>
+</TD>
+
+<TD>Release engineering use this parameter to activate additional targets.
+This parameter forces the recompilation of all static libraries needed
+for the build. This parameter is set to <CODE>YES</CODE> when doing an initial
+build.
+<P>If you download the solver tarball, you do not need to change this parameter.
+If you are creating the build tools, you must set this parameter to <CODE>YES</CODE>.
+</P>
+</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>URD_ONLY</CODE>
+</TD>
+
+<TD>Defaults to the <CODE>WORK_STAMP</CODE> value. This parameter is used to
+differentiate between different formats generated by the UNO IDL compilers.
+URD is the binary format.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>USE_NEWCHARSET</CODE>
+</TD>
+
+<TD>Specifies to change to a new character set. Release engineering used
+this parameter to introduce new functionality.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>USE_NEW_RSC</CODE>
+</TD>
+
+<TD>Specifies to change to a new resource compiler. Release engineering
+used this parameter to introduce new functionality.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>USE_NAMESPACE</CODE>
+</TD>
+
+<TD>If this parameter is set to TRUE, it supports the use of namespaces
+in C++. Release engineering used this parameter to introduce new functionality.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>VCL</CODE>
+</TD>
+
+<TD>The build process uses this parameter as a compiler define. Release
+engineering used this parameter to introduce new functionality.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>WORK_STAMP</CODE>
+</TD>
+
+<TD>The build process inserts this parameter in the CVS source tree to
+identify the source that corresponds to a particular build, for example
+SRC569.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>XCLASSPATH</CODE>
+</TD>
+
+<TD>This parameter is set to the location of the JDK <CODE>classes.zip</CODE>
+file. This allows you to have a shorter class path for building class files.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>XPVERSION</CODE>
+</TD>
+
+<TD>Specifies what version of <CODE>xp</CODE> is used.</TD>
+</TR>
+</table>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/tools/build_env_param.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/tools/build_env_tools.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/tools/build_env_tools.html?rev=1175537&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/tools/build_env_tools.html (added)
+++ incubator/ooo/ooo-site/trunk/content/tools/build_env_tools.html Sun Sep 25 19:39:08 2011
@@ -0,0 +1,507 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+<meta http-equiv="content-type" content="text/html; charset=us-ascii">
+<title>OpenOffice.org - Build tools</title>
+</head>
+<body>
+<h2>Tools Provided for Building and Installing</h2>
+<p>The following table describes the tools provided to build and
+install the office suite. It also indicates what tree these tools
+reside in after you build. For more information on
+<code>solenv</code> and <code>solver</code>, see Source Trees and
+Output Trees.</p>
+<table border="0" cellspacing="0" cellpadding="5" width="400">
+<tr valign="top">
+<th>Tool</th>
+<th>Location</th>
+<th>Description</th>
+</tr>
+<tr valign="top">
+<td><code>_mkout</code></td>
+<td><code>solenv</code></td>
+<td>A small utility for creating an output tree, normally
+<code>$OUTPATH.$PROEXT</code>, for a project. The <code>dmake</code>
+command executes <code>solenv/$OUTPATH.$PROEXT/bin/_mkout</code>
+when building the first files in a project
+<code>solenv/$OUTPATH.$PROEXT/bin/_mkout</code>. You can also call
+this utility from the command line. The <code>_mkout</code> utility
+is built in the <code>tools</code> module.</td>
+</tr>
+<tr valign="top">
+<td><code>bmp</code></td>
+<td><code>solver</code></td>
+<td>A tool for generating image lists. The <code>bmp</code> tool
+takes a <code>.srs</code> input resource file, searches for the
+individual bitmaps, and creates an image list from them. The image
+lists are used in toolbars. You must include the directory paths of
+the bitmaps. The syntax for this tool is as follows:
+<pre>
+bmp <var>srs-input-resource-file</var> <br>
+<var>path-to-bitmaps</var> <var>location-of-language-dependent-bitmaps</var> 
+</pre>
+<p>For example, the following command creates an image list from
+the resource file <code>appl.srs</code> of the German bitmaps in
+<code>../../win/res</code> to the directory
+<code>/german/testdir</code>:</p>
+<pre>
+% <kbd>bmp ../../wntmsci3/srs/appl.srs ../../win/res 
+/german/testdir ../../wntmsci3/res/49 deut</kbd>
+</pre>
+<p>Note that in this example, you must specify <code>49</code> and
+<code>deut</code> to create a list of the German resources. Note
+that <code>49</code> is part of the destination directory name, and
+<code>deut</code> specifies language-dependent bitmaps mostly taken
+from the module <code>res</code>.</p>
+<p>Use the <code>-f</code> option to write a success message to a
+file. If the BMP_WRITES_FLAG parameter is set, this file is
+checked. The following example creates an image list for German,
+and writes a log to the <code>../../common/misc</code>
+directory:</p>
+<pre>
+% <kbd>bmp ../../wntmsci3/srs/appl.srs ../../win/res 
+../../wntmsci3/res/49 deut -f ../../common/misc</kbd>
+</pre>
+<p>For this tool to work on UNIX systems, you must set the
+<code>DISPLAY</code> variable properly. You must also be able to
+access the UNIX system. A Win32 version of this tool is available,
+with a GUI. This tool is built in the module
+<code>svtools</code>.</p>
+</td>
+</tr>
+<tr valign="top">
+<td><code>build</code></td>
+<td><code>solenv</code></td>
+<td>
+<p>This utility iterates through the module directories, spawning
+<code>dmake</code> in each module directory. The <code>prj/build.lst</code>
+list specifies the build prerequisites and a build sequence is determined.</p>
+<p><code>build</code> is aliased to <code>"perl $SRC_ROOT/solenv/bin/build.pl"</code></p>
+<p>The <code>build</code> utility is located at
+<code>solenv/$OUTPATH/bin/build.pl</code>.</p>
+<p>For more information on the build utility refer to the <a href="tools/build.html">detailed documentation</a>.
+<p>For more information
+on the <code>dmake</code> tool, see <a href="#dmake">dmake</a>.
+<p>The command line options for <code>build</code> are as
+follows:</p>
+<p><code>-file</code></p>
+<p>Specifies the temporary file that is created to support the set
+of commands that need to be executed. This option is mandatory.</p>
+<p><code>-all</code></p>
+<p>Specifies to build all module dependencies. The
+<code>build</code> utility builds these modules and delivers
+them.</p>
+<p><code>-get</code></p>
+<p>Checks out the latest source of the project from the CVS tree
+using the <code>$WORK_STAMP</code> tag string. <b>Note</b> that
+this will not work for OpenOffice.org checkouts</p>
+<p><code>-listall</code></p>
+<p>Lists the order that the modules are built in. This list appears
+in the file specified by the option <code>-file</code>.</p>
+<p><code>-make</code></p>
+<p>Specifies which <code>make</code> utility to run, for example
+<code>dmake</code> on Linux, Solaris, or Mac OS X. The
+<code>make</code> utility is built in the <code>tools</code> module
+directory.</p>
+<p>All unknown parameters are handed over to
+<code>dmake</code>.</p>
+</td>
+</tr>
+<tr valign="top">
+<td><code>cc, cpp.lcc</code></td>
+<td><code>solenv</code></td>
+<td>Wrapper script for preprocessing <code>.c</code> files with
+carriage return and line feed line ends.
+<p>Needed for Solaris only because the Workshop C compiler on
+Solaris (<code>SUNWspro</code>) cannot handle multiline macros in
+files with MS-DOS line end convention.</p>
+</td>
+</tr>
+<tr valign="top">
+<td><code>checkdll</code></td>
+<td><code>solenv</code></td>
+<td>This performs a simple test-it tries to load the library. This
+executable is wrapped in a shell script called
+<code>checkdll.sh</code>.</td>
+</tr>
+<tr valign="top">
+<td><code>cppumaker</code></td>
+<td><code>solver</code></td>
+<td>Generates <code>file.hpp</code> and <code>file.hdl</code> from
+the type library or registry database <code>applicat.rdb</code>.
+The <code>.hpp</code> files are the class definition of the UNO IDL
+files. The <code>.hdl</code> files are included in the
+<code>.hpp</code> files and contain definitions. This utility is
+built in the module <code>codemaker</code> and is located in the
+<code>solver</code> tree.
+<p>You can use the following options with the
+<code>cppumaker</code> tool:</p>
+<p><code>-O</code><var>path</var></p>
+<p>The <i>path</i> parameter describes the root directory for the
+generated output. The output directory tree is generated under this
+directory.</p>
+<p><code>-T</code><var>name</var></p>
+<p>The <var>name</var> parameter specifies a type or a list of
+types. The <code>cppumaker</code> tool generates output for this
+type. If you do not specify a <code>-T</code> option, then the
+<code>cppumaker</code> tool generates output for all types. For
+example, <code>com.sun.star.uno.XInterface</code> is a valid
+type.</p>
+<p><code>-B</code><var>name</var></p>
+<p>The <var>name</var> parameter specifies the base node. The
+<code>cppumaker</code> tool searches all types under this node. The
+default is the root directory of the registry files.</p>
+<p><code>-L</code></p>
+<p>For Win32 only. Generates the <code>getCppuType</code> function
+in a short form. Only the name and TypeClass of the type are
+used.</p>
+<p><code>-C</code></p>
+<p>The <code>getCppuType</code> function is generated with
+comprehensive type information.</p>
+<p><code>-G</code></p>
+<p>Use this option to generate only target files which do not
+exist.</p>
+<p><code>-Gc</code></p>
+<p>Use this option to generate only target files whose content will
+be changed.</p>
+<p>The following is an example of using the <code>cppumaker</code>
+tool with some of the options available:</p>
+<p><code>%</code> <kbd>cppumaker -C -BUCR -O../$OUTPATH.$PROEXT/inc
+$SRC_ROOT/solver/$UPD/$OUTPATH.$PROEXT/bin/applicat.rdb</kbd></p>
+</td>
+</tr>
+<tr valign="top">
+<td><code>deliver</code></td>
+<td><code>solenv</code></td>
+<td>Copies headers, generated headers, binaries, shared libraries,
+resources, and so on to <code>solver</code>. The file
+<var>module-name</var><code>/prj/d.lst</code> describes where to
+locate each file, and where to deliver it to.
+<p>Formerly, the <code>deliver</code> tool could also correct the
+include path for the delivered include files to the <code>solver</code>
+tree. These were marked with <code>hedabu</code> in the
+<code>d.lst</code> file. This directed <code>deliver</code> to build
+a new header file by merging header files. Surplus comments and
+empty lines were removed.</p>
+<p><code>hedabu</code> functionality meanwhile (SRC680 m209) got
+removed for the main development code line.</p>
+</td>
+</tr>
+<tr valign="top">
+<td><a name="dmake"></a><code>dmake</code></td>
+<td><code>solenv</code></td>
+<td>A make utility similar to <code>GNU make</code>, used when building OOo.
+<p>For more information on <code>dmake</code>, see the <a href=
+"dmake/index.html">dmake page</a> or for a description of
+OpenOffice.org makefiles see <a href="build_env_mkfiles.html">our
+description</a>.</p>
+<p>Some useful additional <code>dmake</code> switches and targets
+are also available, as follows:</p>
+<p><code>dmake debug=true</code></p>
+<p>Compiles with debug information.</p>
+<p><code>dmake depend=true</code></p>
+<p>Removes dependency information, dependencies are regenerated on
+the next <code>dmake</code> run.</p>
+<p><code>dmake -v -p</code></p>
+<p>Dump out the make file as it is running, provides lots of
+information.</p>
+<p><code>dmake -u</code></p>
+<p>Rebuild everything in the current directory. The use of the
+<code>-u</code> flag can result in unnecessary builds of objects
+because of the recursive nature of the dependencies. Do not use
+this option unless you are sure you understand what you are doing.
+Using this option can cause the following problems:</p>
+<ul>
+<li>The <code>dmake</code> tool tries to rebuild the generated
+headers, because they are in the dependency list
+(<code>.dpc</code>). This causes an error because the generated
+headers are built elsewhere.</li>
+<li>Some object files appear in more than one target. When
+<code>dmake</code> uses one of these object files in a build, it
+updates the timestamp on the file. The <code>dmake</code> tool then
+uses this timestamp to ensure that the object file is built in the
+correct order, and also to apply the correct build switches to the
+object file. If this timestamp is ignored, <code>dmake</code>
+builds the object a second time, this time with incorrect
+switches.</li>
+</ul>
+<p><code>dmake killobj</code></p>
+<p>Remove all objects for sources in the current directory.</p>
+<p><code>dmake killsrs</code></p>
+<p>Remove search resource string files from the current
+directory.</p>
+<p><code>dmake killres</code></p>
+<p>Remove resource files from the current directory.</p>
+<p><code>dmake killdef</code></p>
+<p>Remove existing built targets.</p>
+<p>The default alias of <code>dmake</code> is as follows:
+<code>dmake product=full</code></p>
+</td>
+</tr>
+<!--
+<tr VALIGN=TOP>
+<TD>
+<CODE>include</CODE>
+</TD>
+
+<TD>
+<CODE>solenv</CODE>
+</TD>
+
+<TD>This parses the database generated by the <CODE>incparse</CODE> tool and
+writes the include statements to standard output. If you want to add an
+include statement for a specific class, struct, typedef, or macro in your
+source code, you can use the include tool to get the correct include statement
+for it. You can also use this tool with text editors such as <CODE>vi</CODE>
+or <CODE>emacs</CODE>.</TD>
+</TR>
+
+<tr VALIGN=TOP>
+<TD>
+<CODE>incparse</CODE>
+</TD>
+
+<TD>
+<CODE>solver</CODE>
+</TD>
+
+<TD>Win32 only. The <CODE>incparse</CODE>, or include parse tool generates
+a database of all C and C++ data types. You can use this tool to find the
+location of a header file. For example, if you know that a class called
+<CODE>string</CODE> exists, you can check this database to find the header
+file for this class.</TD>
+</TR>
+-->
+<tr valign="top">
+<td><code>javadep</code></td>
+<td><code>solenv</code></td>
+<td>Creates Java dependency files. These files are stored in
+<var>module-name</var>/<code>$OUTPATH$PROEXT/misc/*.dpj</code>
+files. This utility is similar to the <code>makedepn</code>
+utility. It resides in the <code>solenv</code> tree.</td>
+</tr>
+<tr valign="top">
+<td><code>javamaker</code></td>
+<td><code>solver</code></td>
+<td>Like the <code>cppumaker</code> tool, this generates Java files
+from the type library or registry database
+<code>applicat.rdb</code>. This utility is built in the module
+<code>codemaker</code> and is located in the <code>solver</code>
+tree.
+<p>The syntax is as follows:</p>
+<p><code>javamaker [-options] file_1 ... file_n</code></p>
+<p>You can use the following options with the
+<code>javamaker</code> tool:</p>
+<p><code>-O</code><var>path</var></p>
+<p>The <var>path</var> parameter describes the root directory for
+the generated output. The output directory tree is generated under
+this directory.</p>
+<p><code>-T</code><var>name</var></p>
+<p>The <var>name</var> parameter specifies a type or a list of
+types. The <code>javamaker</code> tool generates output for this
+type. If you do not specify a <code>-T</code> option, then the
+<code>javamaker</code> tool generates output for all types. For
+example, <code>com.sun.star.uno.XInterface</code> is a valid
+type.</p>
+<p><code>-B</code><var>name</var></p>
+<p>The <var>name</var> parameter specifies the base node. The
+<code>cppumaker</code> tool searches all types under this node. The
+default is the root directory of the registry files.</p>
+</td>
+</tr>
+<tr valign="top">
+<td><code>ldump</code></td>
+<td><code>solenv</code></td>
+<td>Dumps all the symbols of a library and filters the symbols by
+discarding all that contain one of the entries in a
+<code>.flt</code> file. This output is used to build the
+<code>.def</code> files.
+<p>The tools <code>ldump2.exe</code> and <code>ldump3.exe</code>
+perform similar functions. The <code>.flt</code> file is used to
+limit the number of exported symbols.</p>
+<p>On UNIX platforms, map files perform a similar function.</p>
+</td>
+</tr>
+<tr valign="top">
+<td><code>lzip</code></td>
+<td><code>solver</code></td>
+<td>Generates an install package.</td>
+</tr>
+<tr valign="top">
+<td><code>makedepn</code></td>
+<td><code>solenv</code></td>
+<td>This tool generates dependencies for source files. If you
+introduce new source files, makedepn executes automatically at make
+time. The syntax for this tool is irregular. Command line
+parameters are as follows:
+<p><code>-I:</code> <var>pathname</var></p>
+<p>Include files in the specified paths.</p>
+<p><code>-E:</code> <var>pathname</var></p>
+<p>Exclude dependent files in the specified paths.</p>
+<p><code>-O</code></p>
+<p>Output file.</p>
+<p><code>-V</code></p>
+<p>Verbose mode.</p>
+<p><code>-D</code></p>
+<p>Debug mode.</p>
+<p>Thus dependencies are not hard-coded into the makefiles but are
+generated at make time. The output dependency list file is created
+as <code>filename.dpc</code> in the following directory:</p>
+<p><var>module-name</var><code>/$INPATH/misc</code></p>
+<p>The <code>makedepn</code> tool is built in the
+<code>tools</code> module.</p>
+</td>
+</tr>
+<tr valign="top">
+<td><code>mksvconf</code></td>
+<td><code>solenv</code></td>
+<td>A minor utility that provides information about the underlying
+system. For example, it provides information about the byte size of
+integers, byte alignment, and so on. The <code>mksvconf</code>
+utility is built in the <code>tools</code> module.
+<p>It creates a <code>svconf.h</code> file in the
+<code>tools/include</code> directory.</p>
+</td>
+</tr>
+<tr valign="top">
+<td><code>msg_filter</code></td>
+<td><code>solenv</code></td>
+<td>A Perl script that contains a list of redundant messages from
+the compiler that cannot be removed. It filters these redundant
+messages from the compiler. It resides in
+<code>solenv/bin</code>.</td>
+</tr>
+<tr valign="top">
+<td><code>rdbmaker</code></td>
+<td><code>solver</code></td>
+<td>Maintains and merges <code>.rdb</code> files for different
+projects.</td>
+</tr>
+<!--
+<tr valign="top">
+<td><code>registerimplementations</code></td>
+<td><code>solenv</code></td>
+<td>This tool registers and unregisters the following in the
+registry database (<code>applicat.rdb</code>):
+<ul type="DISC">
+<li>Shared libraries (DLLs)</li>
+<li>Class names</li>
+<li>URLs of jar files</li>
+</ul>
+<p>Command line options are as follows:</p>
+<p><code>-register</code></p>
+<p>Register the implementations.</p>
+<p><code>-revoke</code></p>
+<p>Unregister the implementations.</p>
+<p>The <code>registerimplementations</code> tool is built in the
+module <code>usr</code>.</p>
+<p><b>Note:</b> This tool is no longer used.</p>
+</td>
+</tr>
+-->
+<tr valign="top">
+<td><code>regview<br>regmerge</code></td>
+<td><code>solver</code></td>
+<td>These are tools for viewing and manipulating the registry
+(<code>applicat.rdb</code>). This tool is built in the module
+<code>registry</code>.</td>
+</tr>
+<tr valign="top">
+<td><code>rsc, rsc2</code></td>
+<td><code>solver</code></td>
+<td>This resource compiler generates the <code>.res</code> and
+<code>.srs</code> resource files. The <code>rsc2</code> tool is
+called from within the <code>rsc</code> utility. For more
+information, run these commands with the <code>-h</code> option.
+These tools are built in the <code>rsc</code> module.</td>
+</tr>
+<tr valign="top">
+<td><code>rscdep</code></td>
+<td><code>solenv</code></td>
+<td>This tool generates dependencies for resource files
+(<code>filename.src</code>). The <code>rscdep</code> tool is the
+resource compiler equivalent of <code>makedepn</code>. In other
+words, the tool generates resource file dependencies similar to
+<code>makedepn</code>. The <code>rscdep</code> tool creates the
+output dependency list file in the
+<var>module-name</var><code>/$OUTPATH.$PROEXT/misc</code> directory
+as <var>filename</var><code>.dpr</code>. The <code>rscdep</code>
+tool is built in the <code>tools</code> module.</td>
+</tr>
+<tr valign="top">
+<td><code>rscpp</code></td>
+<td><code>solenv</code></td>
+<td>Resource compiler preprocessor.</td>
+</tr>
+<tr valign="top">
+<td><code>sbllink</code></td>
+<td><code>solver</code></td>
+<td>Merges interface descriptions for BASIC modules.</td>
+</tr>
+<tr valign="top">
+<td><code>scpcomp</code></td>
+<td><code>solver</code></td>
+<td>Script particle compiler. Generates <code>.par</code> files
+from <code>.scp</code> files. The <code>scplink</code> tool uses
+the <code>.par</code> files to create installation configuration
+files.</td>
+</tr>
+<tr valign="top">
+<td><code>scplink</code></td>
+<td><code>solver</code></td>
+<td>Creates installation configuration files from <code>.par</code>
+files. The <code>setup</code> program uses these <code>.ins</code>
+installation configuration files.</td>
+</tr>
+<tr valign="top">
+<td><code>setsolar</code></td>
+<td><code>solenv</code></td>
+<td>
+<p>This is not used in OpenOffice.org, it is used in StarOffice
+builds.</p>
+<!--
+This information is out of date.  I cant fix this, so commenting out.
+
+<p>Sets environment variables from a database.
+It generates a shell script that you must run the <CODE>source</CODE> command
+on. It is built in the <CODE>tools</CODE> module. 
+<P>The <CODE>stand.lst</CODE> file specifies the platforms to build on, and
+a list of the modules to build. It also contains references to two files:
+a <CODE>.ini</CODE> file and a <CODE>.lst</CODE> file. The <CODE>.ini</CODE>
+file specifies the configuration compiler pathnames that are needed to
+build. The <CODE>.lst</CODE> lists the module directories and the
+dependencies between these modules.
+-->
+</td>
+</tr>
+<tr valign="top">
+<td><code>svidl</code></td>
+<td><code>solver</code></td>
+<td>The View application IDL compiler. This tool has now been
+superseded by <code>unoidl</code> but is still used in places. This
+tool is built in the module <code>idl</code>.</td>
+</tr>
+<tr valign="top">
+<td><code>unocpp</code></td>
+<td><code>solver</code></td>
+<td>This is the UNO IDL preprocessor. This tool is built in the
+module <code>idl</code>.</td>
+</tr>
+<tr valign="top">
+<td><code>unoidl</code></td>
+<td><code>solver</code></td>
+<td>IDL compiler for <code>.idl</code> files, supplied with
+backends for C++, Java, documentation, and so on. For more
+information, run this command with the <code>-h</code> option. This
+tool is built in the module <code>unoidl</code>.</td>
+</tr>
+<tr valign="top">
+<td><code>zipdep</code></td>
+<td><code>solenv</code></td>
+<td>Generates dependencies between zipped files. The
+<code>zipdep</code> tool is derived from version 2.0.1 of the
+common zip utility.</td>
+</tr>
+</table>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/tools/build_env_tools.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/tools/code_Metrics.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/tools/code_Metrics.html?rev=1175537&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/tools/code_Metrics.html (added)
+++ incubator/ooo/ooo-site/trunk/content/tools/code_Metrics.html Sun Sep 25 19:39:08 2011
@@ -0,0 +1,349 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+  <meta http-equiv="content-type"
+ content="text/html; charset=ISO-8859-1">
+  <title>Code Metrics OOo 1.0.3</title>
+</head>
+<body>
+<h1>Code Metrics for OpenOffice.org <br>
+</h1>
+<br>
+<table cellpadding="2" cellspacing="2" border="1"
+ style="width: 100%; text-align: left;">
+  <caption>File Counts for OpenOffice.org 1.0.3<br>
+  </caption><tbody>
+    <tr>
+      <td style="vertical-align: top;">Filetype<br>
+      </td>
+      <td style="vertical-align: top;">total<br>
+      </td>
+      <td style="vertical-align: top;">details<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">C++<br>
+      </td>
+      <td style="vertical-align: top;">12877<br>
+      </td>
+      <td style="vertical-align: top;">6455 cxx, 6337 Header, 35 cpp<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Bitmaps<br>
+      </td>
+      <td style="vertical-align: top;">6923<br>
+      </td>
+      <td style="vertical-align: top;">5761 bmp, 606 xpm, 312 ico, 244
+gif<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Documentation (*.html)<br>
+      </td>
+      <td style="vertical-align: top;">3747<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Directories<br>
+      </td>
+      <td style="vertical-align: top;">3321<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Interface Descriptions (*.idl)<br>
+      </td>
+      <td style="vertical-align: top;">2403<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Makefiles (*.mk)<br>
+      </td>
+      <td style="vertical-align: top;">1722<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">C<br>
+      </td>
+      <td style="vertical-align: top;">1138<br>
+      </td>
+      <td style="vertical-align: top;">437 c, 701 Header <br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Java<br>
+      </td>
+      <td style="vertical-align: top;">668<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Resource files<br>
+      </td>
+      <td style="vertical-align: top;">1245<br>
+      </td>
+      <td style="vertical-align: top;">677 src, 568 hrc<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Perl <br>
+      </td>
+      <td style="vertical-align: top;">22<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">setup partikel<br>
+      </td>
+      <td style="vertical-align: top;">57<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">Assemler<br>
+      </td>
+      <td style="vertical-align: top;">14<br>
+      </td>
+      <td style="vertical-align: top;">7 asm, 7 s<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">awk<br>
+      </td>
+      <td style="vertical-align: top;">24<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">sh<br>
+      </td>
+      <td style="vertical-align: top;">21<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">and some more ...<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">&gt; 35000 file<br>
+      </td>
+      <td style="vertical-align: top;"><br>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<br>
+<h2>Lines of code statistic</h2>
+these statistic are based on tools from <a
+ href="http://www.dwheeler.com/sloccount/">http://www.dwheeler.com/sloccount/</a><br>
+It's missing the file types of idl, makefile (*.mk), documentation
+files (samples, templates, online help, odk documentation). Maybe
+somebody has the time to extend the scripts, so that we can include
+statistics for these as well.<br>
+<br>
+<a href="http://www.dwheeler.com/sloccount/"></a>
+<table cellpadding="2" cellspacing="2" border="1"
+ style="text-align: left; width: 100%;">
+  <caption>Lines of Code (LOC) for OpenOffice.org 1.0.3<br>
+  </caption><tbody>
+    <tr>
+      <td style="vertical-align: top;">LOC (total)<br>
+      </td>
+      <td style="vertical-align: top;">C++<br>
+      </td>
+      <td style="vertical-align: top;">ANSI C<br>
+      </td>
+      <td style="vertical-align: top;">Java<br>
+      </td>
+      <td style="vertical-align: top;">Perl<br>
+      </td>
+      <td style="vertical-align: top;">sh<br>
+      </td>
+      <td style="vertical-align: top;">yacc<br>
+      </td>
+      <td style="vertical-align: top;">asm<br>
+      </td>
+      <td style="vertical-align: top;">objc<br>
+      </td>
+      <td style="vertical-align: top;">lex<br>
+      </td>
+      <td style="vertical-align: top;">awk<br>
+      </td>
+      <td style="vertical-align: top;">sed<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">3169180<br>
+      </td>
+      <td style="vertical-align: top;">2923571<br>
+      </td>
+      <td style="vertical-align: top;">140278<br>
+      </td>
+      <td style="vertical-align: top;">75179<br>
+      </td>
+      <td style="vertical-align: top;">9484<br>
+      </td>
+      <td style="vertical-align: top;">8005<br>
+      </td>
+      <td style="vertical-align: top;">6321<br>
+      </td>
+      <td style="vertical-align: top;">1803<br>
+      </td>
+      <td style="vertical-align: top;">1741<br>
+      </td>
+      <td style="vertical-align: top;">1598<br>
+      </td>
+      <td style="vertical-align: top;">1197<br>
+      </td>
+      <td style="vertical-align: top;">3<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">92.5 %<br>
+      </td>
+      <td style="vertical-align: top;">4.43 %<br>
+      </td>
+      <td style="vertical-align: top;">2.37 %<br>
+      </td>
+      <td style="vertical-align: top;">0.3 %<br>
+      </td>
+      <td style="vertical-align: top;">0.25 %<br>
+      </td>
+      <td style="vertical-align: top;">0.20 %<br>
+      </td>
+      <td style="vertical-align: top;">0.06 %<br>
+      </td>
+      <td style="vertical-align: top;">0.05 %<br>
+      </td>
+      <td style="vertical-align: top;">0.05 %<br>
+      </td>
+      <td style="vertical-align: top;">0.04 %<br>
+      </td>
+      <td style="vertical-align: top;">0 %<br>
+      </td>
+    </tr>
+  </tbody>
+</table>
+<br>
+<table cellpadding="2" cellspacing="2" border="1"
+ style="text-align: left; width: 100%;">
+  <caption>Lines of Code (LOC) for OpenOffice.org 1.1<br>
+  </caption><tbody>
+    <tr>
+      <td style="vertical-align: top;">LOC (total)<br>
+      </td>
+      <td style="vertical-align: top;">C++<br>
+      </td>
+      <td style="vertical-align: top;">Java<br>
+      </td>
+      <td style="vertical-align: top;">ANSI C<br>
+      </td>
+      <td style="vertical-align: top;">Perl<br>
+      </td>
+      <td style="vertical-align: top;">sh<br>
+      </td>
+      <td style="vertical-align: top;">yacc<br>
+      </td>
+      <td style="vertical-align: top;">objc<br>
+      </td>
+      <td style="vertical-align: top;">asm<br>
+      </td>
+      <td style="vertical-align: top;">lex<br>
+      </td>
+      <td style="vertical-align: top;">awk<br>
+      </td>
+      <td style="vertical-align: top;">csh<br>
+      </td>
+      <td style="vertical-align: top;">python<br>
+      </td>
+      <td style="vertical-align: top;">sed<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;">4297681<br>
+      </td>
+      <td style="vertical-align: top;">3909719</td>
+      <td style="vertical-align: top;">184299<br>
+      </td>
+      <td style="vertical-align: top;">182442<br>
+      </td>
+      <td style="vertical-align: top;">12384<br>
+      </td>
+      <td style="vertical-align: top;">7890<br>
+      </td>
+      <td style="vertical-align: top;">6533<br>
+      </td>
+      <td style="vertical-align: top;">1741<br>
+      </td>
+      <td style="vertical-align: top;">1663<br>
+      </td>
+      <td style="vertical-align: top;">1360<br>
+      </td>
+      <td style="vertical-align: top;">1049<br>
+      </td>
+      <td style="vertical-align: top;">55<br>
+      </td>
+      <td style="vertical-align: top;">18<br>
+      </td>
+      <td style="vertical-align: top;">3<br>
+      </td>
+    </tr>
+    <tr>
+      <td style="vertical-align: top;"><br>
+      </td>
+      <td style="vertical-align: top;">90.97 %<br>
+      </td>
+      <td style="vertical-align: top;">4.29 %<br>
+      </td>
+      <td style="vertical-align: top;">3.98 %<br>
+      </td>
+      <td style="vertical-align: top;">0.29%<br>
+      </td>
+      <td style="vertical-align: top;">0182 %<br>
+      </td>
+      <td style="vertical-align: top;">0.15%<br>
+      </td>
+      <td style="vertical-align: top;">0.04%<br>
+      </td>
+      <td style="vertical-align: top;">0.04%<br>
+      </td>
+      <td style="vertical-align: top;">0.03%<br>
+      </td>
+      <td style="vertical-align: top;">0.02%<br>
+      </td>
+      <td style="vertical-align: top;">0%<br>
+      </td>
+      <td style="vertical-align: top;">0%<br>
+      </td>
+      <td style="vertical-align: top;">0%<br>
+      </td>
+    </tr>
+  </tbody>
+</table>
+for 1.1 also hxx are computed, not for 1.0.3.<br>
+<br>
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/tools/code_Metrics.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/ooo/ooo-site/trunk/content/tools/code_Metrics.html
------------------------------------------------------------------------------
    svn:executable = *



Mime
View raw message