Apache OpenOffice Wiki - User contributions [en]

User:RockRockOn

2006-03-31T20:09:07Z

RockRockOn:

Also known as '''evilyoda''' on IRC

Skills:
*Java
*Ruby
*Visual Basic
*MySQL
*Some PHP
*Even less C/C++

Interests:
*Computational Linguistics
*Grammar Checker Development

Chart2

2006-03-31T20:04:24Z

RockRockOn: /* OOoBuild */ add wikilinks for ccache and icecream

This page gathers information about the new chart implementation of OpenOffice.org.

HERE - ADD some more information to make it look less empty...

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "[[ccache]]" and "[[icecream]]" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

TODO : Describing the vanilla build process.

==== OOoBuild ====

TODO : Describing the OOoBuild build process.

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code

== Developping for the new chart module ==

The common steps.

== Documentation ==

== Some useful information ==

* Web page : http://graphics.openoffice.org/chart/chart.html
* specs : http://specs.openoffice.org/chart/index.html
* Current CWS Name : [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]

[[Category:Calc issues]]

Chart2

2006-03-31T20:01:00Z

RockRockOn: /* Vanilla */

This page gathers information about the new chart implementation of OpenOffice.org.

HERE - ADD some more information to make it look less empty...

== Compiling the new chart module ==

The first step anyone need to achieve before starting to develop on the chart module
is compiling OpenOffice.org with the needed modifications for the new chart module.
OpenOffice.org provides two main ways to compile it : the "Vanilla" way and the
"OOoBuild" way. Let's explain what they are and the differences between those two
ways.

=== Compiling OpenOffice.org : the theory ===

==== Vanilla ====

Vanilla is the "standard" way to compile OOo. To compile OOo the "Vanilla" way,
you only need to download the sources, unzip them, and follow the instructions given
on the page [Add a link to the build steps from]. We will give Chart-specific details
about this in the following sections.

==== OOoBuild ====

To make it simple, OOoBuild is a "wrapper" around the OpenOffice.org build process
to make compiling OOo more straight-forward. Some of the enhancements added are :

* patches for known compiling problems
* integration with "ccache" and "icecream" to speed-up the process
* linux distribution specific compiling steps (specific splash screen for Fedora...)

So, to compile OOo with OOoBuild, just just need to download OOoBuild and put the
OOo standard sources in a specific directory.

=== Compiling OpenOffice.org : the practice ===

==== Commmon steps ====

First of all before starting to compile anything, you will need to install all the
dependencies and tools needed for the compiling steps. On the Tools project page,
you should find all the information on the "Building the source" section :

http://tools.openoffice.org/

There, you should read the different sub-sections, they will give you a nice
introduction on how everything works. You should also notice that the steps are
different on each OS.

==== Vanilla ====

TODO : Describing the vanilla build process.

==== OOoBuild ====

TODO : Describing the OOoBuild build process.

==== The bugs reported and the solutions. ====

During the compiling step, you will not be able to compile the whole code

== Developping for the new chart module ==

The common steps.

== Documentation ==

== Some useful information ==

* Web page : http://graphics.openoffice.org/chart/chart.html
* specs : http://specs.openoffice.org/chart/index.html
* Current CWS Name : [[http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Id=1074&Path=SRC680%2Fchart2mst3 chart2mst3]]

[[Category:Calc issues]]

User:RockRockOn

2006-03-31T19:56:06Z

RockRockOn:

Skills:
*Java
*Ruby
*Visual Basic
*MySQL
*Some PHP
*Even less C/C++

Interests:
*Computational Linguistics
*Grammar Checker Development

Building with ooobuild

2006-03-31T19:42:11Z

RockRockOn: /* Requirements */ add a note about automake version

== 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>
----
 

=== configure ===


The build process is pretty complicated; you have a choice
of commands now; although running both won't actually hurt:

./autogen.sh # only for the CVS version
./configure # the packaged version


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.


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.


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.


=== 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)

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.

=== download ===


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.


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.


=== make ===


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>.


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.


== See also ==

*[[Installing]]
*[[Tinderbox Setup]]
*[[BuildSpeedup]]

[[Category: Development]]

Talk:Product Release

2005-12-02T03:32:33Z

RockRockOn: what's beyond 2.0.x?

== 2.x? 3.0? ==

What information do we have for plans beyond the 2.0.x releases?