2008/12/23 <[email protected]> > ---------- Forwarded message ---------- > From: Christian Lins <[email protected]> > To: [email protected] > Date: Mon, 22 Dec 2008 12:31:14 +0100 > Subject: Re: [dev] new developer > Hello and welcome to you! >
Thank you for you kind welcome Christian. :) Silly me wrote en email to this mailing list without subscribing, and I only just realised that is why I have no reply! > The OOo wiki contains useful information and tutorials. Some of them are > outdated as things are changing fast ;-) > Yes, I have noticed this. There is a lot of information in there, and unfortunately there is a lot of partial repetition. This guide here seemed to be the most complete, up to date and easy to follow: http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows > >> I thought that doing some easy bug fixes would be a nice way to get to >> 'know >> the ropes'. I would also be very happy to work closely with someone if >> they >> have a little mini-project going on and they would like some assistance >> with >> that. >> >> Should I just grab the latest source code, get it building and then look >> for >> something in the issue tracker and submit patches? >> > > Yes, that sounds very good. > Thank you for confirming that this is a reasonable approach. > > Perhaps you should try to build OOo for yourself to get in touch with > Subversion, modules, etc. > Checkout a recent milestone on an operating system of your choice (building > on Linux is imho very easy compared to Windows/Solaris) from the Subversion > repository (e.g. svn://svn.services.openoffice.org/ooo/tags/DEV300_m37). > > Btw. you can browse the sourcecode via > http://svn.services.openoffice.org/opengrok . > > Then if you have successfully build OOo yourself, I would try to apply and > test some patches, verify bugs, etc. > > Don't hesitate to ask questions, hacking OOo can be a challenging task ;-) > > Good luck! > > Christian > Ok, so for now I would like to build on Windows because I don't have a Linux box at the moment unfortunately. So I followed the guide I mentioned above closely. I am trying to build using the tarballs because I thought that would be easiest (then once I have that working and am comfortable with my build setup then start using the SVN). I downloaded all the additional files needed (JDK, Win SDK etc), and copied them to the appropriate directories. I then ran configure successfully, then bootstrap, the winenv.set.sh script and then finally the build command. All went well for about the first 2 hours. Many modules built and no complaints. Then it exits the build with an error in the 'Python' module. I get 3 linker errors: socketmodule.obj : error LNK2019 unresolved external symbol __imp__freeaddri...@4 referenced in function _setipaddr socketmodule.obj : error LNK2019 unresolved external symbol __imp__getaddri...@16 referenced in function _setipaddr socketmodule.obj : error LNK2019 unresolved external symbol __imp__getnamei...@28 referenced in function _makeipaddr Stop dmake: Error code 2, while making './ wntmsci12.pro/misc/build/so+built_so_python' ERROR: Error 65280 occurred while making /cygdrive/d/dev/OOo_Builds/DEV300_m37/python I am using Visual Studio Express 2008, on Win XP and have tried both OOO300_m9 and DEV300_m37 with what appears to be the same result. If anyone can give me some advice on this it would be much appreciated. Regards Robert Black
