Bjorn and Rene,
I went to http://download.openoffice.org/2.4.3/source.html and got all of
the source packages at the bottom of the page except the "extensions".
I don't have a testautomation package. I will try to find and download a
version of this from the site. In the short term it would be good if
someone could add an instruciton to do this to the documentation.
As for the configure step, the "building on windows" page just gives two
examples - no explanation of what the options mean. I had a lot of trouble
with Mozilla - I don't really want to build it, I downloaded the built
libraries, but I had to use both --disable-build-mozilla and the "not
really official" -disable-nss-module to get configure to be happy. Also, it
says not to use paths with spaces in, but the example uses paths with
spaces.
I have tried --disable-qadevooo but it made no difference.
Many thanks for your help,
Richard
----- Original Message -----
From: "Björn Michaelsen" <[email protected]>
To: <[email protected]>
Sent: Tuesday, December 22, 2009 1:26 PM
Subject: [dev] Re: Build error
Am Tue, 22 Dec 2009 10:27:39 -0000
schrieb "Richard Whitehead" <[email protected]>:
Hello, I hope someone can help...
I'm trying to build Open Office for the first time. I'm an
experienced developer on Windows using Visual Studio, but I'm not
used to the unix/cygwin style of build. I've followed the
instructions for building on windows and it all seemed fine (although
the configuration step needed a bit of guesswork) until I got to the
actual build, which is failing:
Hi Richard,
Unfortunately I am not familiar with the build error you describe, but
I'll try to help anyway. Could you please give some additional info:
- Do you have a folder "testautomation" in your source tree?
- How did you get the source? Did you download a source package? If so,
which one? Or did you download via SCM (Mercurial/SVN)?
- If you used a source-tarball, how did you unpack it?
Im not involved in the way source-tarballs are created (using SCM is
so simple now with mercurial), but there is a also "testautomation"
tarball, maybe you need to add that one? If that is the case, we should
indeed update the docs to reflect that.
Also I would be interested in the parts of the configure step that you
needed guesswork for and if we can make the instructions on that more
explicit/helpful.
Best Regards,
Bjoern Michaelsen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
