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 Italian?
His logs s
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, so I assume John isn't
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. So I don't
> > have a
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
--
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
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
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 fin
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:
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 installi
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 t
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, Patrici
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 so
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
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 and
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/
wntmsci12.pr
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"
--with
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):
ERROR:
So I've taken courage thanks also to the work done by Patricia Shanahan on
building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows 10, and
I've sorted through the first few obstacles and my build has now been
running for 5-6 hours without any trouble. Until now that is. It just broke
wh
18 matches
Mail list logo
