RSS Feed
Bookmark to Delicious
Friday, 18 Jan 2008
accessibility
api
architecture
automated_tests
base
beta
build
calc
chart
code
community
database
development
directx
document
download
draw
eis
events
export
extensions
features
filter
framework
graphics
gsl
gsoc
gullfoss
import
impress
installation
iso26300
java
l10n
localization
mac
netbeans
odf
ooo
ooocon
ooocon2008
ooocon2009
open
opendocument
openoffice
openoffice.org
pdf
performance
porting
qa
quality
quaste
release
renaissance
security
snapshot
software
specification
spreadsheet
staroffice
statistics
sun
survey
testing
toolkit
tools
usability
user-experience
video
web
wiki
writer
xml
- show all articles
Friday, 18 Jan 2008
Jens-Heiner Rechtien
With a new major release of OpenOffice.org we finally get the opportunity to update some of our build tools. Especially compilers could use some refreshing, the default ones used by Sun OOo release engineering date from 2003/2004. A pretty complete list of the compilers used for production builds of OOo for the major platforms and distributions can be found here.
The planned changes in detail:
- Solaris SPARC, Solaris x86: We (Sun OOo release engineering) plan to switch to SunStudio 12 (09/07). This release has better support for boost, which is becoming more prominent in our code base. More important, SunStudio 12 is freely available (registration required) and thus is already the compiler of choice for most Solaris developers. It looks like we can safely drop support for older SunStudio compilers after the switch, please notify me if this is not the case.
- Linux: Most likely the current gcc-4.2.2 will be the future default Linux compiler for Sun OOo developers. We will still support older compilers, way back to gcc-3.3.x, they are needed for MacOSX 10.3 and OS/2. As soon as these two platforms have upgraded to gcc-4.x we will be able to drop support for gcc-3.x completely as everyone else seems to use gcc-4.x.
- Windows: Most probably we will switch to .Net 2008 once it is released, for now we'll use .Net 2005. We will still support .Net 2003 for a while to protect the investment some OOo developers have made into this compiler, but this can't last forever.
tags: build compiler openoffice.org
Digg this
Comments
I guess there are no good free compilers for Windows that could be an option also?
I have seen a few open source projects look to try and support open source compilers so they are really practicing what they preach.
Posted by Al on January 19, 2008 at 03:06 AM CET #
Mac OS X 10.3 is no longer supported by the OpenOffice.org project officially.
Posted by Shaun McDonald on January 19, 2008 at 11:32 PM CET #
I am very surprised that windows development is not being ported to the mono environment, so that participants can have a FOSS environment.
Posted by Bob Harvey on January 21, 2008 at 10:18 AM CET #
@Al: Why, yes, there is a good free compiler to build OOo! It's the Mingw version of gcc. The port is done by Takashi Ono with the help of Vladimir Glazunov. It's also possible to build OOo on Windows with the Visual Express versions, which are free as in beer. The blog article is about production compilers which are used by release engineering, often we support other compilers as well.
@Shaun: Thanks for the info! I'm looking forward to the day we no longer need to support gcc-3.3.x with it's broken parser. Could you please update the production compiler page?
@Bob: I sense a misconception here. I guess that with porting to mono you mean porting to Windows-Forms and other parts of the .Net-framework as implemented in Mono. Openoffice,org has it's own framework, down to the level of Windows API calls. No MFS or such things. And since this framework is as well open source as the rest of OOo we have as much a FOSS environment as it's possible to have on Windows. Actually, we have a few pieces of .Net stuff in there, mostly for C# language bindings.
Posted by Jens-Heiner Rechtien on January 21, 2008 at 01:54 PM CET #