On 16.12.2010 18:20, Alexandro Colorado wrote:

On Thu, Dec 16, 2010 at 10:43 AM, Mathias Bauer<[email protected]>  wrote:

Hi Gerry,

On 17.12.2010 01:18, Gerry's Hotmail wrote:

My name is Gerry Escobar and I am interested in donating some time in
building OpenIffice.



I consider myself probably not a novice but not an expert programmer
either.
I have an old Borland C++ 3.1 compiler which I bought when I decided to
learn C++ programming.  It's been decades since I set aside my programming
skills.  After reading your website while trying to get a copy of OO today
and also now that I'm beginning to get more time in my hands to do some
other things, I thought perhaps I can get back into continuing my learning
of C++.  If you think you might be able to use me with my old C++
compiler,
I am willing to donate some time in building OO.  If not in the
programming
area, perhaps in the testing side of things.

If you want to work on Windows, you will need to switch to the Microsoft C++
compiler. There is a cost-free version of it available ("Visual Studio
Express").

I think there was some ways to do it from gcc, but the way to build
has changed starting 3.2. So that work most be reimplemented.
Really, though I admire Tono for his heroic effort to build OOo with gcc on Windows, it's not what I would recommend for beginners. It requires a patched version of mingw that usually only works for a limited number of OOo versions and it is even slower than the VC++ based build (that already is much slower than gcc on Linux on the same hardware).

So my recommendation is: if the VC++ compiler should be avoided, avoid Windows too.

Regards,
Mathias

--
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Oracle: http://blogs.sun.com/GullFOSS
Please don't reply to "[email protected]".
I use it for the OOo lists and only rarely read other mails sent to it.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to