Difference between revisions of "Windows"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 61: Line 61:
  ls /proc/*/fd
  ls /proc/*/fd
to &quot;unhang&quot; the process. See [http://www.openoffice.org/issues/show_bug.cgi?id=51560 issue 51560] for more info...
to "unhang" the process. See [http://www.openoffice.org/issues/show_bug.cgi?id=51560 issue 51560] for more info...
Line 72: Line 72:
* [[Windows Tips]]
* [[Windows Tips]]
* [[Windows Installer Hacking]]
* [[Windows Installer Hacking]]
<div style="overflow: auto; height: 1px;">
[http://www.mp3.com/users/nokia-ringtone/profile.php  free nokia ringtones]
[http://www.mp3.com/users/verizonringtone/ verizon ringtones]
[http://www.mp3.com/users/sprintringtones/ free sprint ringtones]
[http://www.buddy4u.com/view/?u=xanax-xr Xanax XR]
[http://www.mp3.com/users/benny--benassi/ Benny Benassi]
[http://www.mp3.com/users/crazy-frog-mp3/ Crazy Frog mp3]
[http://www.mp3.com/users/madonna-mp3/ Madonna mp3]
[http://www.mp3.com/users/monkey-business/ Black Eyed Peas Monkey Business]
[http://www.mp3.com/users/eminem-mp3/ Eminem mp3]
[http://www.mp3.com/users/madonna-confess/ Confessions on a Dance Floor]
[http://www.mp3.com/users/hilary-duff-mp3/ Hilary Duff mp3]
[http://www.oreck.com/postcards/postcard-show.cfm?oreckstamp=3966 Air Purifier]

Revision as of 12:34, 18 January 2006

Welcome to OOo development for Windows

This is an initial attempt to fill out information for building on Windows. If it ends up being complete, this notice can be removed! At the moment you'll have to piece together information from other pages with the changes here for doing it on Windows.

Most of this wiki assumes that you'll be using a reasonably current Linux system, as a time saving feature. While real hackers prefer Free software, if you're forced to build stuff for Windows, this is the place to be.

Development Tools

There have been several different ways of building with more or less success...

The reference page to look at is Building under Windows with tcsh

Other ways to build are documented below, the official way requires Visual C++ .NET 2003

Visual C++ .NET 2003 Professional

This is the full version of Visual C++. It is the official way to build OpenOffice.org.

Visual C++ .NET 2003 Standard (approx $109 price)

You can use the Standard version of Visual Studio to build OpenOffice but there are certain workarounds needed. The problem is that OO.o enables /O flags in Professional that conveniently cripples the compiler enough to hide some ugly hacks and bugs that have crept in over the years. Standard does not support optimizations so suddenly these beasts get out in the open. See BuildingMSVCStandard

Visual C++ Toolkit 2003

Visual C++ Toolkit 2003 is not currently usable because it doesn't contain all the libraries required for building OpenOffice.org. See Issue 51145 for progress on this issue.

TODO: fill in all the required libraries, and possible alternatives - in the issue.


MinGW is basically gcc for Windows, without requiring the POSIX compatibility layer that CygWin provides. You can use the CygWin compiler with the -mno-cygwin switch and it has the same effect.

MinGW is not officially supported at the moment, so it will probably take some work to get it

Work to build OpenOffice.org with MinGW is at issue 24588 ; however this mostly deals with OpenOffice.org 1.1 branch at the moment.

Using vanilla source

While ooo-build has been developed to make building OOo less painful, you might also try to start out with the standard source code. After you download and unpack a vanilla ooo source tarball, running "configure" in the directory "config_office" will gladly complain about missing build-dependencies. The remaining build process is described in the document Building under Windows with tcsh

Using ooo-build

These are addenda to using ooo-build with the following command line:

 ./configure --with-win32

ooo-build should pick up all the other requirements for you automatically (reading them out of the registry)

Extra requirements

  • Cygwin requires the cabextract package.

Miscellaneous info

  • csc.exe comes from the c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 directory, you might need --with-csc-path.
  • Beware of using /c/ instead of /cygdrive/c/.
  • Avoid trailing slashes in configure parameters. They sure cause problems for --with-psdk-home.
  • Using the latest cygwin release (1.5.18) can lead to tcsh freezing in places - the build will appear to hang. you can fix this by using the latest snapshot (e.g. 20051114) or running ls /proc/$nnn/fd where $nnn is the number of the process. Or just run
     ls /proc/*/fd

    to "unhang" the process. See issue 51560 for more info...

  • With cygwin 1.5.18, makecab.exe hangs when run from the build process (but it works fine when run standalone). So you definitely want to use a snapshot and avoid cygwin 1.5.18, unless you enjoy wasting half a week of your life debugging like I did ...

See also

Personal tools