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 that is necessary. Could you test your Windows 10 build on a Windows 7 machine? Or send me the output - that may be quicker than waiting for my Windows 10 build to go through.

On 9/19/2016 1:46 PM, John D'Orazio wrote:
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, Patricia Shanahan <p...@acm.org> wrote:

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 somewhere that maybe using 64 bit cygwin can resolve the
occupied addresses and child_fork_process errors. I made an attempt at
getting the build environment ready in 64 bit cygwin but configure is
complaining about not finding Visual Studio C++, while this does not
happen
in 32 bit cygwin (I'm passing in the with-cl-home flag so it shouldn't
have
any problem finding it... I'm reading it has something to do with registry
keys, idk I have to look into this better).

...


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to