The wiki is the place where all the documentation is gathered.
Here are some suggestions:
OpenOffice.org Developer's Guide
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide
is a good starting point. If you want to develop macros or extensions, it is
All I can say is that it works form me now. I have successfully built
DEV300_m83 under Windows.
-Mensaje original-
De: Kristján Bjarni Guðmundsson [mailto:kristjanbja...@gmail.com]
Enviado el: lunes, 05 de julio de 2010 0:42
Para: dev@openoffice.org
Asunto: Re: [dev] Problems building
No, this does not work, configure translates any junction (because cygpath -w)
does. Just try to put the OpenOffice.org source tree in a short absolute
pathname like c:\ooo. Will report to cygwin.
In cases like this, I suggest to use linkd.exe to create
Thank you.
-Mensaje original-
De: Mathias Bauer [mailto:nospamfor...@gmx.de]
Enviado el: jueves, 01 de julio de 2010 13:15
Para: dev@openoffice.org
Asunto: [dev] Documentation about necessary configure parameters for Windows
updated in the building guide
Hi,
motivated by one of our
Hello. I can't build OpenOffice.org under Windows, because when the postprocess
stage is reached, it fails.
I have already run rebaseall and peimageall, which are supposed to solve this
issue.
This is Windows XP Service Pack 3.
Here are the error messages:
Building module postprocess
Solved. The cause was that pathnames where too long. The argument list of the
rebase command (long list of DLLs).
In cases like this, I suggest to use linkd.exe to create a junction point.
linkd.exe is included with the operating system.
See you tomorrow.
Aviso legal – Comisión Nacional del
?
-Mensaje original-
De: Mathias Bauer [mailto:nospamfor...@gmx.de]
Enviado el: martes, 29 de junio de 2010 10:24
Para: dev@openoffice.org
Asunto: Re: [dev] Issues building under windows xp: patch
Hi Ramón,
On 28.06.2010 19:32, Ramón García Fernández wrote:
After studying the failures
Finally I managed to isolate the problem. It is a problem with case.
The Microsoft Visual C++ express defines the LIB environment variable
(vcvars32.bat). The Cygwin system translates it to lowercase lib. Openoffice
build system defines uppercase LIB, and leaves lib untouched. When the
No, not only unnecessary (see my last mail). It can't work because one can not
put multiple paths under a single LIBPATH option. See
http://msdn.microsoft.com/en-us/library/1xhzskbe%28v=VS.80%29.aspx
You can specify only one directory for each /LIBPATH option you enter
-Mensaje
Yes, I am using vcvars32.bat. Otherwise the compiler does not run.
In a cygwin shell without running vcvars32:
$ /cygdrive/c/Archivos\ de\ programa/Microsoft\ Visual\ Studio\
9.0/VC/bin/cl.exe
/cygdrive/c/Archivos de programa/Microsoft Visual Studio 9.0/VC/bin/cl.exe:
error while loading
\
--enable-werror \
--with-external-tar=d:/OOo/ext_sources \
--disable-binfilter
By adjusting the pathes you should be able to use that.
Regards,
Mathias
On 29.06.2010 19:11, Ramón García Fernández wrote:
Yes, I am using vcvars32.bat. Otherwise the compiler does not run.
In a cygwin
After studying the failures in the components that link against libxml2
(libxslt and xmlsecurity) I am convinced that there is a bug in the build
system. The makefiles (tg_ext.mk) defines the INCLUDE variable on Windows
platforms, used by Microsoft compilers to define the search path for header
It looks like I forgot to attach the patch.
Aviso legal – Comisión Nacional del Mercado de Valores
Este mensaje y, en su caso, los ficheros que lleve incorporados, está dirigido
exclusivamente a su destinatario y es de carácter confidencial. Si fuere
recibido por error o se tuviere
This is weird. So all the other modules have been built correctly?
cd into ./DEV300_m83/instsetoo_native
and do build.pl verbose=true
(so you will se commands invoked).
I had a issue building in the instsetoo_native/util directory. But there was an
error message. I solved it entering it, doing
I thought that it was clear that the error was that the appropiate path to the
libxml2.lib was not given to the linker command line. Unfortunately, there is
no easy way to change the language compiler messages. I am going to install the
English version of Visual C++ Express 2008. Anyway, here
I used libxml2 bundled in OOo. But the compilation of both libxslt and
libxmlsecurity did not include the solver/../lib in the linker path. I had to
add it by hand.
-Mensaje original-
De: Mathias Bauer [mailto:nospamfor...@gmx.de]
Enviado el: Wednesday, June 23, 2010 8:07 PM
Para:
I have solved the issue with libxslt by building by hand. Now it fails with
python:
(Spanish messages translated by me)
--
build.pl verbose=true
dmake: Warning: -- Found file corresponding to virtual
to compile cleanly under Windows? I can't see how,
if these lines are not uncommented.
-Mensaje original-
De: Ramón García Fernández [mailto:ram...@cnmv.es]
Enviado el: Monday, June 21, 2010 1:32 PM
Para: dev@openoffice.org
Asunto: [dev] Issue building OpenOffice under Windows
Hello, I am
Hello, I am builing OpenOffice under Windows using Cygwin and Visual Studio
Express. I am having some issues, some small, and others not so small.
I am using the DEV300_m79 milestone.
This is the last error that I am fighting (sorry for the messages in Spanish, I
could not yet find a way to
19 matches
Mail list logo
