Re: Building on Windows Witj Java8

On 2021-04-25 18:00, Matthias Seidel wrote: > Hi Keith, > > Am 25.04.21 um 23:54 schrieb Keith N. McKenna: >> I am in the process of redoing the template for the Release Notes.Is >> there still a problem with building AOO on Windows with Java 8? If not I >> will delete the Note in The Known

Re: Building on Windows Witj Java8

Hi Keith, Am 25.04.21 um 23:54 schrieb Keith N. McKenna: > I am in the process of redoing the template for the Release Notes.Is > there still a problem with building AOO on Windows with Java 8? If not I > will delete the Note in The Known Issues section. That was fixed with AOO 4.1.8:

Re: building on Windows 10 breaks at guistdio.exe

On 9/20/2016 12:56 AM, John D'Orazio wrote: On Tue, Sep 20, 2016 at 7:50 AM, Ariel Constenla-Haile wrote: On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote: 4.1.3 does have changes to the language library URLs. Has anyone else done a build that included

Re: building on Windows 10 breaks at guistdio.exe

On Tue, Sep 20, 2016 at 7:50 AM, Ariel Constenla-Haile wrote: > On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote: > > 4.1.3 does have changes to the language library URLs. Has anyone else > done a > > build that included Italian? > > His logs say aoo-trunk,

Re: building on Windows 10 breaks at guistdio.exe

On Tue, Sep 20, 2016 at 7:44 AM, Ariel Constenla-Haile wrote: > On Tue, Sep 20, 2016 at 03:22:40AM +0200, John D'Orazio wrote: > > I wound up building in stages, since the build was breaking here and > there. > > I just picked it up from where it left off as I fixed things.

Re: building on Windows 10 breaks at guistdio.exe

On Mon, Sep 19, 2016 at 07:12:29PM -0700, Patricia Shanahan wrote: > 4.1.3 does have changes to the language library URLs. Has anyone else done a > build that included Italian? His logs say aoo-trunk, so I assume John isn't building branch AOO413. NSIS >= 3.* is only on that branch. Regards --

Re: building on Windows 10 breaks at guistdio.exe

On Tue, Sep 20, 2016 at 03:22:40AM +0200, John D'Orazio wrote: > I wound up building in stages, since the build was breaking here and there. > I just picked it up from where it left off as I fixed things. So I don't > have a single output... unless there is a log file that collects various > build

Re: building on Windows 10 breaks at guistdio.exe

Sorry, "output" was ambiguous. I'm not interested in the log files at this time, but in the installation files. I want to try to install the result of your build on a Windows 7 machine. On 9/19/2016 6:22 PM, John D'Orazio wrote: I wound up building in stages, since the build was breaking here

Re: building on Windows 10 breaks at guistdio.exe

4.1.3 does have changes to the language library URLs. Has anyone else done a build that included Italian? On 9/19/2016 6:33 PM, John D'Orazio wrote: I actually did see an error in the packaging phase, but it didn't seem to affect the final output, I still got the setup.exe which worked just

Re: building on Windows 10 breaks at guistdio.exe

I actually did see an error in the packaging phase, but it didn't seem to affect the final output, I still got the setup.exe which worked just fine, and I can open and use soffice.exe just fine after running setup. This is the error I got: ERROR: The following errors occurred in packaging process:

Re: building on Windows 10 breaks at guistdio.exe

I wound up building in stages, since the build was breaking here and there. I just picked it up from where it left off as I fixed things. So I don't have a single output... unless there is a log file that collects various build stages together into one single output? I would also recommend

Re: building on Windows 10 breaks at guistdio.exe

Congratulations! I'm about to do a Windows 10 build on a new machine, so please make sure the step-by-step incorporates all that you learned in the process. I have a specific test I would like run. The current release process calls for doing the Windows builds on Windows 7. I am wondering if

Re: building on Windows 10 breaks at guistdio.exe

I have now successfully completed the build on Windows 10, and after changing the install path of NSIS to one without spaces, packaging also completed successfully. I have added "Windows 10" alongside "Windows 7" and "Windows 8.1" in the Step by Step guide. On Mon, Sep 19, 2016 at 7:50 PM,

Re: building on Windows 10 breaks at guistdio.exe

I had installed 64-bit Cygwin installed here before I started on compiling AOO. I hit problems, and had to go to the recommended 32-bit Cygwin. However, things have changed a bit since then, so it may be worth seeing if it works. On 9/19/2016 8:59 AM, John D'Orazio wrote: ... I also read

Re: building on Windows 10 breaks at guistdio.exe

I installed some more things in my build environment such as the Windows Drive Kit and I enabled the atl flags. I cleaned the whole build and started over again with new config and using the multiprocessor and multi threading capability, and have now made it close to the end of the build. Only the

Re: building on Windows 10 breaks at guistdio.exe

Please excuse the delay responding - I put it aside hoping that someone with more knowledge would respond, and then got involved in other things. One possibility is that solver/420/wntmsci12.pro/xml/ was partially built due to an earlier failure. I suggest deleting solver/420/wntmsci12.pro

Re: building on Windows 10 breaks at guistdio.exe

Patricia you are correct, after a few more attempts the desktop module did build successfully. Now I'm up to the postprocess module, with this error: Entering /cygdrive/d/source/aoo-trunk/main/postprocess/packcomponents dmake: Error: -- `/cygdrive/d/source/aoo-trunk/main/solver/420/

Re: building on Windows 10 breaks at guistdio.exe

If it can be of any use to understand better the problem, I'm using this configuration: SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0" ./configure --with-frame-home="$SDK_PATH" --with-psdk-home="$SDK_PATH" --with-midl-path="$SDK_PATH/bin" --with-directx-home="D:\Microsoft_DirectX_SDK_June_2010"

Re: building on Windows 10 breaks at guistdio.exe

I've never seen this failure before. The only suggestion I can make is to retry. That sometimes fixes failed builds. On 9/14/2016 12:39 PM, John D'Orazio wrote: ... dmake: '../../../wntmsci12.pro/bin/guistdio.exe' removed. 1 module(s): desktop need(s) to be rebuilt Reason(s):

Re: Building on Windows

Could this patch also be modified to apply to 4.1.2? It may be the issue preventing me from doing Windows builds of that release. On 2/10/2016 3:57 PM, Damjan Jovanovic wrote: icu supports building on Cygwin using Cygwin's make, but for some bizarre reason AOO builds it with MSVC's nmake using

RE: Building on Windows

nal Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Sunday, February 14, 2016 17:29 > To: dev@openoffice.apache.org > Subject: Re: Building on Windows > > On 2/14/2016 1:34 PM, Patricia Shanahan wrote: > > > > > > On 2/14/2016 1:32 PM, Patrici

Re: Building on Windows

On 2/14/2016 1:34 PM, Patricia Shanahan wrote: On 2/14/2016 1:32 PM, Patricia Shanahan wrote: On 2/5/2016 6:55 AM, Damjan Jovanovic wrote: On Fri, Feb 5, 2016 at 4:52 PM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: My build finished! The

Re: Building on Windows

On 2/5/2016 6:55 AM, Damjan Jovanovic wrote: On Fri, Feb 5, 2016 at 4:52 PM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: My build finished! The next problem is to run it. I have hit two problems, one minor. The minor problem is that

Re: Building on Windows

On 2/14/2016 1:32 PM, Patricia Shanahan wrote: On 2/5/2016 6:55 AM, Damjan Jovanovic wrote: On Fri, Feb 5, 2016 at 4:52 PM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: My build finished! The next problem is to run it. I have hit two problems,

Re: Building on Windows

Thank you. Also recompiled icu 200 times successfully, so we can be pretty sure that patch is correct. I've made a bug for this issue (https://bz.apache.org/ooo/show_bug.cgi?id=126840) and committed the patch in r1729921: #i126840# - Windows/MSVC build often fails in main/icu The build script

Re: Building on Windows

I have made changes to https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step to record what I learned during this process. It would be helpful if someone with a Windows machine could attempt a build using the latest version of those instructions, to test them.

Re: Building on Windows

Your patch works for me. On 2/10/2016 3:57 PM, Damjan Jovanovic wrote: icu supports building on Cygwin using Cygwin's make, but for some bizarre reason AOO builds it with MSVC's nmake using makefiles generated by a Perl script and even completely bypassing ./configure (makefile.mk has

Re: Building on Windows

I have experienced a major step backwards. My build attempts all fail: == $ build --All build -- version: 275224 = Building module instsetoo_native = Entering

Re: Building on Windows

Thanks. Silly typo, when I've typed "build --all" dozens of times over the last couple of weeks. On 2/10/2016 2:22 PM, Damjan Jovanovic wrote: I can reproduce that. The "--All" needs to be in lowercase, ie. "build --all". On Wed, Feb 10, 2016 at 11:20 PM, Patricia Shanahan

Re: Building on Windows

I can reproduce that. The "--All" needs to be in lowercase, ie. "build --all". On Wed, Feb 10, 2016 at 11:20 PM, Patricia Shanahan wrote: > I have experienced a major step backwards. My build attempts all fail: > >

Re: Building on Windows

Thanks. I'll take it for a test drive tomorrow. On 2/10/2016 3:57 PM, Damjan Jovanovic wrote: icu supports building on Cygwin using Cygwin's make, but for some bizarre reason AOO builds it with MSVC's nmake using makefiles generated by a Perl script and even completely bypassing ./configure

Re: Building on Windows

icu supports building on Cygwin using Cygwin's make, but for some bizarre reason AOO builds it with MSVC's nmake using makefiles generated by a Perl script and even completely bypassing ./configure (makefile.mk has CONFIGURE_ACTION+= $(PERL) ..$/..$/..$/..$/..$/createmak.pl

Re: Building on Windows

The icu module has a complicated build with scripts generating makefiles... I am not sure what approach to even take debugging this, but some ideas might be: * make a copy of a main/icu[/wntmsci12.pro] directory that builds and a copy of one that doesn't, then diff the files to see what's

Re: Building on Windows

I have already done some of this. The key difference between failing and non-failing is whether layoutex is built early or later in the build. See the attached files for sample build outputs. I believe layoutex has a dependency on icuin.lib that is not properly declared in the makefile etc.,

Re: Building on Windows

Hi Patricia, Patricia Shanahan schrieb: My build finished! The next problem is to run it. I have hit two problems, one minor. The minor problem is that https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7 has incorrect paths using "OpenOffice" rather than

Re: Building on Windows

On Fri, Feb 5, 2016 at 4:52 PM, Regina Henschel wrote: > Hi Patricia, > > Patricia Shanahan schrieb: > >> My build finished! >> >> The next problem is to run it. I have hit two problems, one minor. The >> minor problem is that >> >>

Re: Building on Windows

My build finished! The next problem is to run it. I have hit two problems, one minor. The minor problem is that https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7 has incorrect paths using "OpenOffice" rather than "Apache_OpenOffice". The more serious

Re: Building on Windows

Hi Patricia, I had sometimes curious build breaks because of parallelism and virus scan. So please try to make a build without any parallelism and disable virus scan. Additional benefit: without parallelism, the log tells you the actual module order. Kind regards Regina Patricia Shanahan

Re: Building on Windows

On Thu, Feb 4, 2016 at 11:47 PM, Patricia Shanahan wrote: > On 2/4/2016 12:40 PM, Regina Henschel wrote: > >> Hi Patricia, >> >> Patricia Shanahan schrieb: >> >>> I think maybe I need to clean up and start again. What is the best way >>> to clean, short of doing a fresh checkout?

Re: Building on Windows

On 2/4/2016 12:40 PM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: I think maybe I need to clean up and start again. What is the best way to clean, short of doing a fresh checkout? I remove the output-tree manually Starting in main: find . -maxdepth 2 -name "wntmsci12*" |

RE: Building on Windows

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Thursday, February 4, 2016 13:48 > To: dev@openoffice.apache.org > Subject: Re: Building on Windows > > On 2/4/2016 12:40 PM, Regina Henschel wrote: > > Hi Patricia, > > >

Re: Building on Windows

On 2/4/2016 3:36 PM, Damjan Jovanovic wrote: On Thu, Feb 4, 2016 at 11:47 PM, Patricia Shanahan wrote: On 2/4/2016 12:40 PM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: I think maybe I need to clean up and start again. What is the best way to clean,

Re: Building on Windows

Remember what I told you about main/icu: it doesn't build deterministically, sometimes it fails and sometimes it passes for no apparent reason, keep cleaning and rebuilding in its directory until it builds then "deliver" and continue as before. On Thu, Feb 4, 2016 at 4:21 PM, Patricia Shanahan

Re: Building on Windows

Thanks for the reminder. My plan for this morning was to search my mail archive for "icuin". I had hoped that getting rid of MP would get rid of this sort of non-determinism. On 2/4/2016 6:30 AM, Damjan Jovanovic wrote: Remember what I told you about main/icu: it doesn't build

Re: Building on Windows

I had 25 consecutive "build --all" attempts fail, at different places, due to the retryable errors. The general behavior, and the fact that the frequency of failure varies from environment to environment, supports the theory that the failures are due to poorly managed multiprocessing.

RE: Building on Windows

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Wednesday, February 3, 2016 08:16 > To: dev@openoffice.apache.org > Subject: Re: Building on Windows > [ ... ] > > I have some hypotheses about my current problems. Is there a master

Re: Building on Windows

I got icu to build. Here is my latest failure: C:\OpenOfficeDev\Trunk\main\offapi\com\sun\star\sdb\XRowSetChangeListener.idl(45) : WARNING, type or identifier doesn't fulfill the UNO naming convention: i_Event dmake: /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/inc/target.mk: line 583:

Re: Building on Windows

That's just a unit test, although main/cppu/qa/makefile.mk should really be ignoring failures in rm: $(MISC)$/$(TARGET).rdb: $(MISC)$/$(TARGET)$/types.urd - rm $@ $(REGMERGE) $@ /UCR $< Try "ENABLE_UNIT_TESTS=NO build" On Thu, Feb 4, 2016 at 6:51 PM, Patricia Shanahan

Re: Building on Windows

I think maybe I need to clean up and start again. What is the best way to clean, short of doing a fresh checkout? Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/Trunk/main/instsetoo_native $ ENABLE_UNIT_TESTS=NO build 2>&1 |tee wk3 build -- version: 275224 = Building module

Re: Building on Windows

Cleaning is covered in https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO which currently seems down? Personally I use "dmake clean" in main, and if I really want to delete absolutely every new file since SVN checkout: svn revert * -R svn status | while read i; do rm -rf "${i:8}";

Re: Building on Windows

Hi Patricia, Patricia Shanahan schrieb: I think maybe I need to clean up and start again. What is the best way to clean, short of doing a fresh checkout? I remove the output-tree manually Starting in main: find . -maxdepth 2 -name "wntmsci12*" | xargs rm -rf In addition delete wntmsci12*

Re: Building on Windows

Yes, thanks. At least, it gets past oox. So one trick for a missing file is to explicitly build and deliver in the directory the file should have come from. Later, I may do a new build from a clean check-out, and try to investigate anomalies. Right now, my objective is to just get it built.

Re: Building on Windows

I am now getting to: Compiling: oox/source/ole/vbacontrol.cxx C:/OpenOfficeDev/Trunk/main/oox/source/ole/vbacontrol.cxx(34) : fatal error C1083: Cannot open include file: 'xmlscript/xmldlg_imexp.hxx': No such file or directory dmake: Error code 2, while making

Re: Building on Windows

That is strange. Does it work if you first do "build" and "deliver" in main/xmlscript? On Wed, Feb 3, 2016 at 1:07 PM, Patricia Shanahan wrote: > I am now getting to: > > Compiling: oox/source/ole/vbacontrol.cxx > C:/OpenOfficeDev/Trunk/main/oox/source/ole/vbacontrol.cxx(34) :

Re: Building on Windows

Yes, there is certainly stuff to investigate. My latest failure is: /usr/bin/cp: missing destination file operand after '/cygdrive/c/OpenOfficeDev/Trunk/main/solver/420/wntmsci12.pro/lib/isvl.lib' Try '/usr/bin/cp --help' for more information.

Re: Building on Windows

Are you using build --all? I am not sure what else could be wrong there. Something probably built in the wrong order. You might have to start from the beginning... On Wed, Feb 3, 2016 at 1:37 PM, Patricia Shanahan wrote: > Yes, there is certainly stuff to investigate. My latest

RE: Building on Windows

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Wednesday, February 3, 2016 03:29 > To: dev@openoffice.apache.org > Subject: Re: Building on Windows > > Yes, thanks. At least, it gets past oox. > > So one trick for a missing

Re: Building on Windows

On 2/3/2016 8:04 AM, Dennis E. Hamilton wrote: -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] Sent: Wednesday, February 3, 2016 03:29 To: dev@openoffice.apache.org Subject: Re: Building on Windows Yes, thanks. At least, it gets past oox. So one trick for a missing

Re: Building on Windows

;>> To: dev@openoffice.apache.org >>> Subject: Re: Building on Windows >>> >>> Yes, thanks. At least, it gets past oox. >>> >>> So one trick for a missing file is to explicitly build and deliver in >>> the directory the file should have co

Re: Building on Windows

On 2/2/2016 9:25 AM, Damjan Jovanovic wrote: On Tue, Feb 2, 2016 at 6:10 PM, Patricia Shanahan wrote: OpenGrok looks and sounds like something I should learn about. I think my next step is to look into the state of python. Matters may have been complicated because I did a

Re: Building on Windows

On 2/2/2016 4:34 PM, Greg Bullock wrote: On 2/1/2016 3:33 PM, Patricia Shanahan wrote: ... Thanks for looking into it. It appears to probably be, ultimately, an issue with TortoiseSVN mangling line endings. I am redoing the checkout using Cygwin's command line svn. Once that is done, I'll

Re: Building on Windows

python had apparently not been built. I don't know why. I was able to get the build going again with "build --all:python". It is now making progress, but from time-to-time I get this sort of failure: ==

RE: Building on Windows

be controlled in what they produce. The problem is using multiple repositories with different approaches. - Dennis > -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Tuesday, February 2, 2016 16:37 > To: dev@openoffice.apache.org > Subject: Re: Buil

RE: Building on Windows

+1 Yep, there it is. Thanks Greg > -Original Message- > From: Greg Bullock [mailto:g...@nwra.com] > Sent: Tuesday, February 2, 2016 18:54 > To: dev@openoffice.apache.org > Subject: Re: Building on Windows > > > > On 2/2/2016 4:37 PM, Patricia Shanahan

Re: Building on Windows

Thanks. On 2/1/2016 11:50 PM, Damjan Jovanovic wrote: According to http://stackoverflow.com/questions/19641685/java-jni-jawt-error-unresolved-external-symbol-imp-jawt-getawt8 you're using a 64 bit JDK instead of a 32 bit one. On Tue, Feb 2, 2016 at 9:40 AM, Patricia Shanahan

Re: Building on Windows

Thanks. Now I get to: = Building module pyuno = Entering /cygdrive/c/OpenOfficeDev/Trunk/main/pyuno/source/module mkout -- version: 1.8 dmake: makefile.mk: line 56: Error: -- Include file pyversion.mk, not found On 2/2/2016 4:18 AM, Damjan Jovanovic wrote: For

Re: Building on Windows

OpenGrok[1] tells me the pyversion.mk file is in main/python; through building it would get delivered to main/solver/... and found by pyuno. Did python not build before pyuno did? pyuno/prj/build.lst lists a dependency on python when PYTHON is defined[2]: bgpupyuno : stoc cpputools

Re: Building on Windows

I've documented this gotcha on both https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step and https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO On Tue, Feb 2, 2016 at 10:29 AM, Patricia Shanahan wrote: > Thanks. > > > On 2/1/2016 11:50 PM,

Re: Building on Windows

For me, main/icu fails to build on Windows about 50% of the time for no apparent reason; I've begun to think it's some sort of build race condition within that module. I haven't seen the buildbots fail there, and nobody else has reported this problem. If this is your problem, the only fix I know

Re: Building on Windows

Good. My latest error is: NMAKE : fatal error U1073: don't know how to make '".\..\..\lib\icuin.lib"' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~2\MICROS~1.0\VC\bin\nmake.exe' : return code '0x2' Stop. dmake: Error code 2, while making './wntmsci12.pro/misc/build/so_built_so_icu' I am

Re: Building on Windows

On Tue, Feb 2, 2016 at 6:10 PM, Patricia Shanahan wrote: > OpenGrok looks and sounds like something I should learn about. > > I think my next step is to look into the state of python. Matters may have > been complicated because I did a "dmake clean" after changing my configure >

Re: Building on Windows

OpenGrok looks and sounds like something I should learn about. I think my next step is to look into the state of python. Matters may have been complicated because I did a "dmake clean" after changing my configure parameters to use a 32 bit JDK, before continuing the steps from configure on.

Re: Building on Windows

On 2/2/2016 4:37 PM, Patricia Shanahan wrote: On 2/2/2016 4:34 PM, Greg Bullock wrote: On 2/1/2016 3:33 PM, Patricia Shanahan wrote: ... Thanks for looking into it. It appears to probably be, ultimately, an issue with TortoiseSVN mangling line endings. I am redoing the checkout using

Re: Building on Windows

On 1/31/2016 6:36 PM, Patricia Shanahan wrote: Now I'm stuck. I got through configure, with warnings. My build attempt failed with: $ build --all build -- version: 275224 = Building module solenv = Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv

Re: Building on Windows

On Mon, 1 Feb 2016 14:08:06 -0800 Patricia Shanahan wrote: > > > On 2/1/2016 12:04 PM, Patricia Shanahan wrote: >> >> >> On 1/31/2016 6:36 PM, Patricia Shanahan wrote: >>> Now I'm stuck. I got through configure, with warnings. My build attempt >>> failed with: >>> >>> $ build --all >>> build --

Re: Building on Windows

On 2/1/2016 12:04 PM, Patricia Shanahan wrote: On 1/31/2016 6:36 PM, Patricia Shanahan wrote: Now I'm stuck. I got through configure, with warnings. My build attempt failed with: $ build --all build -- version: 275224 = Building module solenv = Entering

Re: Building on Windows

On 2/1/2016 2:41 PM, j.nitsc...@ok.de wrote: On Mon, 1 Feb 2016 14:08:06 -0800 Patricia Shanahan wrote: On 2/1/2016 12:04 PM, Patricia Shanahan wrote: On 1/31/2016 6:36 PM, Patricia Shanahan wrote: Now I'm stuck. I got through configure, with warnings. My build attempt failed with: $

Re: Building on Windows

On 2/1/2016 7:00 AM, Damjan Jovanovic wrote: On Mon, Feb 1, 2016 at 4:46 PM, Patricia Shanahan wrote: On 2/1/2016 4:34 AM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: Now I'm stuck. I got through configure, with warnings. Can you please be more

Re: Building on Windows

On Mon, Feb 1, 2016 at 1:49 PM, Patricia Shanahan wrote: > > > On 1/31/2016 11:59 PM, Damjan Jovanovic wrote: > >> On Mon, Feb 1, 2016 at 4:36 AM, Patricia Shanahan wrote: >> >> Now I'm stuck. I got through configure, with warnings. My build attempt >>> failed with:

Re: Building on Windows

Hi Patricia, Patricia Shanahan schrieb: Now I'm stuck. I got through configure, with warnings. Can you please be more specific about the warnings? Are you sure, you start building in instsetoo_native ? Kind regards Regina

Re: Building on Windows

On 2/1/2016 8:34 AM, Damjan Jovanovic wrote: On Mon, Feb 1, 2016 at 1:49 PM, Patricia Shanahan wrote: On 1/31/2016 11:59 PM, Damjan Jovanovic wrote: On Mon, Feb 1, 2016 at 4:36 AM, Patricia Shanahan wrote: Now I'm stuck. I got through configure, with

Re: Building on Windows

After checking out with Cygwin's svn rather than TortoiseSVN, my build failed in "Building module bean" with the following message: Creating library ../../wntmsci12.pro/lib/iofficebean_t1.lib and object ../../wntmsci12.pro/lib/iofficebean_t1.exp

Re: Building on Windows

According to http://stackoverflow.com/questions/19641685/java-jni-jawt-error-unresolved-external-symbol-imp-jawt-getawt8 you're using a 64 bit JDK instead of a 32 bit one. On Tue, Feb 2, 2016 at 9:40 AM, Patricia Shanahan wrote: > After checking out with Cygwin's svn rather than

Re: Building on Windows

On 2/1/2016 4:34 AM, Regina Henschel wrote: Hi Patricia, Patricia Shanahan schrieb: Now I'm stuck. I got through configure, with warnings. Can you please be more specific about the warnings? Are you sure, you start building in instsetoo_native ? I've posted a message in this thread with

Re: Building on Windows

On Mon, Feb 1, 2016 at 4:46 PM, Patricia Shanahan wrote: > On 2/1/2016 4:34 AM, Regina Henschel wrote: > >> Hi Patricia, >> >> Patricia Shanahan schrieb: >> >>> Now I'm stuck. I got through configure, with warnings. >>> >> >> Can you please be more specific about the warnings? >>

Re: Building on Windows

On 1/30/2016 4:59 PM, Patricia Shanahan wrote: On 1/30/2016 3:45 PM, Patricia Shanahan wrote: After a busy couple of months, I am back to trying to build AOO on Windows 8.1. I am following https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7, which seems

Re: Building on Windows

Now I'm stuck. I got through configure, with warnings. My build attempt failed with: $ build --all build -- version: 275224 = Building module solenv = Entering /cygdrive/c/OpenOfficeDev/Trunk/main/solenv /cygdrive/c/OpenOfficeDev/Trunk/main/solenv/bin/mkout.pl: line

Re: Building on Windows

Hi Patricia, Patricia Shanahan schrieb: On 1/30/2016 3:45 PM, Patricia Shanahan wrote: Step: Optional: Get dbghelp.dll (for using the --enable-dbgutil configure option) This step contains the first mention of MS Visual Studio, but seems to assume it is already installed. I do have a version

Re: Building on Windows

Hi Patricia, please follow the link https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Windows in addition. At top of the page is a list with download links and further explanation. Patricia Shanahan schrieb: After a busy couple of months, I am back to trying to

Re: Building on Windows

On 1/30/2016 3:45 PM, Patricia Shanahan wrote: After a busy couple of months, I am back to trying to build AOO on Windows 8.1. I am following https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7, which seems to be the most up-to-date and relevant guide. This

Re: Building on WIndows, revisited

My progress got stopped by a combination of Christmas preparations, work towards an Apache River release, and extreme discouragement. Each time I solved a problem, another one cropped up, and I was not confident in all the decisions I had made along the way. I expect to have more time for OO

Re: Building on Windows 7

Same result when running cygwin as administrator. -- View this message in context: http://openoffice.2283327.n4.nabble.com/Building-on-Windows-7-tp4657909p4657970.html Sent from the Development mailing list archive at Nabble.com.

Re: Building on Windows 7

On 16.01.2014 14:12, jonasalfreds...@gmail.com wrote: Hi, I'm trying to build Open Office from trunk on Windows 7. Had some trouble getting through the configure and bootstrap but finally now building step is starting. A few modules into the build the following error occurs in module jpeg:

Re: Building on Windows 7

Running build a second time produce the following: jonasalfredsson@TOMMY-TUMULT /cygdrive/c/source/aoo-trunk/main/instsetoo_native $ build --all:jpeg build -- version: 275224 = Building module jpeg = Entering /cygdrive/c/source/aoo-trunk/main/jpeg mkdir: cannot create

Re: Building on Windows 7

Hi Jonas, It seems like a privilege issue. Maybe it was caused by cygwin. I think you can run cygwin as administrator again and try. On Fri, Jan 17, 2014 at 12:05 AM, jonasalfreds...@gmail.com jonasalfreds...@gmail.com wrote: Running build a second time produce the following: