Apache OpenOffice Wiki - User contributions [en]

Building with ooobuild

2007-10-20T14:16:57Z

MirkoNasato: removed spam

== Vanilla Up-stream builds ==

See the [http://tools.openoffice.org#Build tools] project for build guides for various platforms.

Also for OS/X see [[MacOSXBuildInstructions]]

For GNU/Linux Sparc, with gcc4.1 & gcj, see [[GNULinuxSparcPorting]]

== ooo-build builds ==

<center>
'''If you are looking for additional building tips for Windows check [[Windows |this]] page first.'''
</center>
----
<br>

=== configure ===

<p>
The build process is pretty complicated; you have a choice
of commands now; although running both won't actually hurt:
</p>
./autogen.sh --with-distro=<b>HelloMum</b> # only for the CVS version
./configure --with-distro=<b>HelloMum</b> # the packaged version

<p>
This will guess which branch snapshot you want to build; if
you have other ideas use the --with-tag option; eg.
<code>--with-tag=src680-m65</code> for a legacy branch.
</p>
<p>
NB. getting your distro right is quite important; values like
SUSE-10.1 (also SLED10), UbuntuDapper, DebianEtch64 may float
your boat. Checkout <code>ls distro-configs</code> to see more.
</p>
<p>
If for some reason you have a 31337 multi-threaded computer,
with great slabs of RAM; you'll want to use --with-num-cpus=8
etc. NB. it's not clever to force the build to swap like a
demented pawnbroker by using an artificially high number; C++
compilation is seriously memory hungry.
</p>
<p>
In particular, building SRC680 requires a recent jdk & a
version of apache-ant. If you use a Novell system, just do:
<code>sudo rug in apache-ant</code>, alternatively download
a package from [http://www.rpmfind.net/linux/rpm2html/search.php?query=apache-ant&submit=Search+..." rpmfind.net] or failing that see [http://ant.apache.org/bindownload.cgi Ant download]
& set the ANT environment variable
appropriately before configuring.
</p>
<h4>Known ./configure parameters</h4>
<ul>
<li><h5>up-stream options</h5><p> - all options are passed through directly
to the internal configure, so they should work nicely here too.</p>
</li>
<li><h5><code>--with-system-<package name></code></h5>
<p>where <package name> is replaced by the package to use. I don't
have a particularly good understanding of its full effects beyond
the fact that it (probably) doesn't then build its own copy of the
package.</p>
<p><b>Examples:</b><br>
<code>--with-system-python</code><br>
<code>--with-system-mozilla</code><br>
<code>--with-system-gcc</code><br>
<code>--with-system-neon</code><br>
<code>--with-system-curl</code><br>
</p>
</li>
<li><h5><code>--without-system-<package name></code></h5>
<p><b>Examples:</b><br>
<code>--without-system-mozilla</code>
</p>
</li>
<li><h5><code>--with-<package or tag>[=value]</code></h5>
<p><b>Examples:</b><br>
<code>--with-lang=en-US</code><br>
<code>--with-build-version="Build 2.0.1.3"</code><br>
<code>--with-distro=Gentoo</code><br>
</p>
</li>
<li><h5><code>--without-<package or tag></code></h5>
<p><b>Examples:</b><br>
<code>--without-myspell-dicts</code><br>
<code>--without-java</code><br>
<code>--without-nas</code><br>
</p>
</li>
<li><h5><code>--enable-<package name></code></h5>
<p><b>Examples:</b><br>
<code>--enable-openldap</code><br>
</p>
</li>
<li><h5><code>--disable-<package name></code></h5>
<p><b>Examples:</b><br>
<code>--disable-openldap</code><br>
<code>--disable-qadevoo</code><br>
<code>--disable-mozilla</code><br>
<code>--disable-access</code><br>
<code>--disable-evolution2</code><br>
</p>
</li>
<li><h5><code>--mandir=<dir></code></h5></li>
</ul>

=== Requirements ===

*A recent version of automake, such as the 1.9 series.
*If you don't have a working Java VM (i.e. any runtime), you should pass <code>--with-java=no</code> to either <code>autogen.sh</code> or <code>configure</code>.
*You need the Archive/Zip module for Perl (perl-Archive-Zip on RPM-based distributions, libarchive-zip-perl on dpkg-based distributions). Alternatively, see instructions[http://ooo.ximian.com/cpan.html] for obtaining Perl modules through CPAN.
*You need the development package for Python (this would be python-devel on RPM-based distributions).
*You need curl and curl-devel.
*You need odbc_config to be present. On SUSE systems, this is in the unixODBC-devel package.
*You need libsndfile and libsndfile-devel.
*If you don't have a recent enough openldap, pass <code>--disable-openldap</code> to <code>autogen.sh</code> or <code>configure</code>.
*You need neon and neon-devel.
*You need qt3 and qt3-devel, or if you don't have the KDE development packages, pass <code>--disable-kde</code> to <code>autogen.sh</code> or <code>configure</code>.
*You need mozilla-nss-devel.
*In SuSE, you need gecko-sdk, mono-devel and cups-devel

=== download ===

<p>
By the time you've upgraded your system to the point that it
has all the packages you need to start building OO.o (mozilla etc. etc.) you're almost at the point that you
can download the bulk of the source. To do this, after a
successful configure simply type: <code>./download</code> and wait.
</p>
<p>
If for whatever reason this fails, you can verify your download
by fetching the equivalent .md5 file & comparing it to
the result of <code>md5sum <archive></code>. The source
archives are http://go-ooo.org/packages/SRC680
- put the source in ooo-build/src.
</p>

=== make ===

<p>
This is the taxing bit - type <code>make</code> and don't forget
to press enter. Quite possibly you want to log the output, so
why not <code>make 2>&1 | tee /tmp/log</code>.
</p>
<p>
Since ooo-build wraps the actual OO.o configuration &
build process, there are a number of internal config checks that
also need to pass. For a first time build it's well worth staying
near the console while everything unpacks, and the internal
configure runs; if that completes without incident - you're
usually into the heavy-duty thumb twiddling.
</p>

== See also ==

*[[Installing]]
*[[Tinderbox Setup]]
*[[BuildSpeedup]]
*[[OpenSUSE Build Instructions]]
*[[SUSE9.3 Build Instructions]]
*[[Ubuntu Build Instructions]]
*OpenOffice.org "Tools" page [http://tools.openoffice.org/dev_docs/build_linux.html]
*[[Build Tool Requirements]]
*[[O3-build|O3 Build]], an ISO image containing all the required software to build OOo on Linux.

[[Category: Development]]

Uno/Java/MavenBundles

2007-01-30T17:26:19Z

MirkoNasato: /* Maven Bundles for Java Uno JARs */

= Maven Bundles for Java Uno JARs =

[http://maven.apache.org Maven] 2 is a popular Java build tool that provides many useful features for building Java projects, including dependency management.

The Java Uno JAR files are available from the Maven Central Repository, so that projects that use Java Uno can fully benefit from Maven dependency management features.

The available JAR files, or ''artifacts'', are
* juh.jar
* jurt.jar
* ridl.jar
* unoil.jar

To include those Java/Uno libraries into your project managed by Maven you'll typically declare the following dependencies in your <code>pom.xml</code>:
<pre>
<dependency>
<groupId>org.openoffice</groupId>
<artifactId>juh</artifactId>
<version>2.1.0</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.openoffice</groupId>
<artifactId>jurt</artifactId>
<version>2.1.0</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.openoffice</groupId>
<artifactId>ridl</artifactId>
<version>2.1.0</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.openoffice</groupId>
<artifactId>unoil</artifactId>
<version>2.1.0</version>
<scope>compile</scope>
</dependency>
</pre>
== Upload Procedure ==

The following information describes how to upload new versions of the JARs to the Maven repository; if you just want to use the JARs you don't need to read it.

The upload procedure is detailed in [http://maven.apache.org/guides/mini/guide-ibiblio-upload.html Guide to uploading artifacts to The Central Repository]. New bundles would be created and uploaded at each OpenOffice.org stable release.

Each ''artifact'' (JAR file) needs to be packaged into a ''bundle'' that also includes an XML file (''pom.xml'') containing information about the artifact, including name, description, version, license, and dependencies.

The values provided in the XML description files are

{| border="1"
! Element || Value
|-
| colspan="2" | '''Common to all artifacts'''
|-
| groupId || org.openoffice
|-
| version || the OOo version that shipped this JAR, e.g.: 2.1.0
|-
| url || http://udk.openoffice.org
|-
| license name || GNU Lesser General Public License, Version 2.1
|-
| license url || http://www.openoffice.org/licenses/lgpl_license.html
|-
| scm url || http://udk.openoffice.org/source/browse/api/
|-
| scm connection || scm:cvs:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
|-
| colspan="2" | '''Artifact: juh'''
|-
| artifactId || juh
|-
| name || OpenOffice.org "javaunohelper" module
|-
| description || Various tools and adapters for Java Uno.
|-
| dependencies || jurt, ridl
|-
| colspan="2" | '''Artifact: jurt'''
|-
| artifactId || jurt
|-
| name || OpenOffice.org "jurt" module
|-
| description || JURT stands for "Java Uno Runtime". The JURT module basically implements Java Uno.
|-
| dependencies || ridl
|-
| colspan="2" | '''Artifact: ridl'''
|-
| artifactId || ridl
|-
| name || OpenOffice.org "ridl" module
|-
| description || The "ridljar" module implements the base types for the Java Uno typesystem, as well as a types access library.
|-
| dependencies || -
|-
| colspan="2" | '''Artifact: unoil'''
|-
| artifactId || unoil
|-
| name || OpenOffice.org "unoil" module
|-
| description || Java class files generated from the IDL Files to create the Java UNO Interface.
|-
| dependencies || ridl
|}

[[Category:Uno:Java]]

Uno/Java/MavenBundles

2007-01-21T11:45:42Z

MirkoNasato: /* Maven Bundles for Java Uno JARs */

= Maven Bundles for Java Uno JARs =

[http://maven.apache.org Maven] 2 is a popular Java build tool that provides many useful features for building Java projects, including dependency management.

This document is a '''proposal''' to make the Java Uno JAR files available to the Maven Central Repository, so that projects that use Java Uno can fully benefit from Maven dependency management features.

The JAR files, or ''artifacts'', to be made available would be
* juh.jar
* jurt.jar
* ridl.jar
* unoil.jar

The upload procedure is detailed in [http://maven.apache.org/guides/mini/guide-ibiblio-upload.html Guide to uploading artifacts to The Central Repository]. New bundles would be created and uploaded at each OpenOffice.org stable release.

Each ''artifact'' (JAR file) needs to be packaged into a ''bundle'' that also includes an XML file (''pom.xml'') containing information about the artifact, including name, description, version, license, and dependencies.

The proposed values to be provided in the XML description files are

{| border="1"
! Element || Value
|-
| colspan="2" | '''Common to all artifacts'''
|-
| groupId || org.openoffice
|-
| version || the OOo version that shipped this JAR, e.g.: 2.1.0
|-
| url || http://udk.openoffice.org
|-
| license name || GNU Lesser General Public License, Version 2.1
|-
| license url || http://www.openoffice.org/licenses/lgpl_license.html
|-
| scm url || http://udk.openoffice.org/source/browse/api/
|-
| scm connection || scm:cvs:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
|-
| colspan="2" | '''Artifact: juh'''
|-
| artifactId || openoffice.org-juh
|-
| name || OpenOffice.org "javaunohelper" module
|-
| description || Various tools and adapters for Java Uno.
|-
| dependencies || openoffice.org-jurt, openoffice.org-ridl
|-
| colspan="2" | '''Artifact: jurt'''
|-
| artifactId || openoffice.org-jurt
|-
| name || OpenOffice.org "jurt" module
|-
| description || JURT stands for "Java Uno Runtime". The JURT module basically implements Java Uno.
|-
| dependencies || openoffice.org-ridl
|-
| colspan="2" | '''Artifact: ridl'''
|-
| artifactId || openoffice.org-ridl
|-
| name || OpenOffice.org "ridl" module
|-
| description || The "ridljar" module implements the base types for the Java Uno typesystem, as well as a types access library.
|-
| dependencies || -
|-
| colspan="2" | '''Artifact: unoil'''
|-
| artifactId || openoffice.org-unoil
|-
| name || OpenOffice.org "unoil" module
|-
| description || Java class files generated from the IDL Files to create the Java UNO Interface.
|-
| dependencies || openoffice.org-ridl
|}

[[Category:Uno:Java]]

Uno/Java/MavenBundles

2006-11-22T20:30:31Z

MirkoNasato: proposal for uploading java uno jars to maven repository

= Maven Bundles for Java Uno JARs =

[http://maven.apache.org Maven] is a popular Java build tool that provides many useful features for building Java projects, including dependency management.

This document is a '''proposal''' to make the Java Uno JAR files available to the Maven Central Repository, so that projects that use Java Uno can fully benefit from Maven dependency management features.

The JAR files, or ''artifacts'', to be made available would be
* juh.jar
* jurt.jar
* ridl.jar
* unoil.jar

The upload procedure is detailed in [http://maven.apache.org/guides/mini/guide-ibiblio-upload.html Guide to uploading artifacts to The Central Repository]. New bundles would be created and uploaded at each OpenOffice.org stable release.

Each ''artifact'' (JAR file) needs to be packaged into a ''bundle'' that also includes an XML file (''pom.xml'') containing information about the artifact, including name, description, version, license, and dependencies.

The proposed values to be provided in the XML description files are

{| border="1"
! Element || Value
|-
| colspan="2" | '''Common to all artifacts'''
|-
| groupId || org.openoffice
|-
| version || the OOo version that shipped this JAR, e.g.: 2.0.4
|-
| url || http://udk.openoffice.org
|-
| license name || GNU Lesser General Public License, Version 2.1
|-
| license url || http://www.openoffice.org/licenses/lgpl_license.html
|-
| scm url || http://udk.openoffice.org/source/browse/api/
|-
| scm connection || scm:cvs:pserver:anoncvs@anoncvs.services.openoffice.org:/cvs
|-
| colspan="2" | '''Artifact: juh'''
|-
| artifactId || openoffice-juh
|-
| name || OpenOffice.org "javaunohelper" module
|-
| description || Various tools and adapters for Java Uno.
|-
| dependencies || openoffice-jurt, openoffice-ridl
|-
| colspan="2" | '''Artifact: jurt'''
|-
| artifactId || openoffice-jurt
|-
| name || OpenOffice.org "jurt" module
|-
| description || JURT stands for "Java Uno Runtime". The JURT module basically implements Java Uno.
|-
| dependencies || openoffice-ridl
|-
| colspan="2" | '''Artifact: ridl'''
|-
| artifactId || openoffice-ridl
|-
| name || OpenOffice.org "ridl" module
|-
| description || The "ridljar" module implements the base types for the Java Uno typesystem, as well as a types access library.
|-
| dependencies || -
|-
| colspan="2" | '''Artifact: unoil'''
|-
| artifactId || openoffice-unoil
|-
| name || OpenOffice.org "unoil" module
|-
| description || Java class files generated from the IDL Files to create the Java UNO Interface.
|-
| dependencies || openoffice-ridl
|}

[[Category:Uno:Java]]