Am 25.03.2018 um 09:16 schrieb Damjan Jovanovic:
> I think I fixed this in 1827695.
Thanks!
>
> Windows still won't build due to a problem in jvmaccess that I am still
> investigating.
Yes, I think that came with revision 1827615:
make: *** No rule to make target
'/cygdrive/e/slave14/aoo-win7/
I think I fixed this in 1827695.
Windows still won't build due to a problem in jvmaccess that I am still
investigating.
On Fri, Mar 23, 2018 at 6:26 PM, Matthias Seidel wrote:
> Correction, BuildBot says Revision 1827459.
>
> Regards,
>
> Matthias
>
>
> Am 23.03.2018 um 17:23 schrieb Matthias
Correction, BuildBot says Revision 1827459.
Regards,
Matthias
Am 23.03.2018 um 17:23 schrieb Matthias Seidel:
> Next one! ;-)
>
> With revision 1827456 I get:
>
> ...
> **
> ERROR: ERROR: Missing files
> in function: remove_Files_Without_Sourced
Next one! ;-)
With revision 1827456 I get:
...
**
ERROR: ERROR: Missing files
in function: remove_Files_Without_Sourcedirectory
**
... analyzing files ...
preparing 1 extension blob for language en-US:
Hi Damjan,
Am 14.03.2018 um 05:04 schrieb Damjan Jovanovic:
> That's good :).
>
> I tried to look at 127731, but in the process discovered a far worse issue:
> https://bz.apache.org/ooo/show_bug.cgi?id=127732
If you uninstall AOO, is everything back to normal?
Matthias
>
> Damjan
>
>
> On Tue,
That's good :).
I tried to look at 127731, but in the process discovered a far worse issue:
https://bz.apache.org/ooo/show_bug.cgi?id=127732
Damjan
On Tue, Mar 13, 2018 at 11:15 PM, Matthias Seidel <
matthias.sei...@hamburg.de> wrote:
> Am 13.03.2018 um 17:54 schrieb Damjan Jovanovic:
> > I've
Am 13.03.2018 um 17:54 schrieb Damjan Jovanovic:
> I've added back the deleted map file I forgot to revert, and have forced a
> rebuild on the Windows bot.
Thanks!
Looks good so far, my local build is far beyond the point where the
error occurred. ;-)
I know you are very busy at the moment, but c
I've added back the deleted map file I forgot to revert, and have forced a
rebuild on the Windows bot.
On Tue, Mar 13, 2018 at 3:52 PM, Matthias Seidel wrote:
> Am 13.03.2018 um 04:19 schrieb Damjan Jovanovic:
> > Hi
> >
> > Thank you.
> >
> > Fiddling with the main/cppuhelper/source/makefile.mk
Am 13.03.2018 um 04:19 schrieb Damjan Jovanovic:
> Hi
>
> Thank you.
>
> Fiddling with the main/cppuhelper/source/makefile.mk to reintroduce the map
> file while keeping the other changes did not help, so it doesn't seem like
> a case of exporting a symbol that wasn't exported before.
>
> I've reve
Hi
Thank you.
Fiddling with the main/cppuhelper/source/makefile.mk to reintroduce the map
file while keeping the other changes did not help, so it doesn't seem like
a case of exporting a symbol that wasn't exported before.
I've reverted all the changes to main/cppuhelper in r1826602 while I
inve
Hi
Now I prefer the idea of still continuing to support cross-building of
AOO32 on Win64. AOO64 would be built opt-in (at least for now), by passing
an --enable-win64 flag to ./configure that enables building AOO64 on Win64,
but without that flag the traditional AOO32 would still be cross-built.
T
Hi Damjan,
Maybe you already have seen it (buildbot revision 1826428):
"ERROR: error 65280 occurred while making
/cygdrive/e/slave14/aoo-win7/build/main/svtools/prj"
https://ci.apache.org/projects/openoffice/buildlogs/win/main/svtools/wntmsci12.pro/misc/logs/prj.txt
Regards,
Matthias
Am 1
Hi Damjan,
I think your last commit [1] breaks the Win32 build:
"ERROR: error 65280 occurred while making
/cygdrive/c/Source/aoo/main/cppuhelper/source" in my local build.
See a more detailed log from our buildbot:
https://ci.apache.org/projects/openoffice/buildlogs/win/main/cppuhelper/wntmsci1
On Mon, Mar 5, 2018 at 3:29 PM, Patricia Shanahan wrote:
>
>
> On 3/4/2018 11:27 PM, Damjan Jovanovic wrote:
> ...
>
>> But there is a simple way to both keep the 64->32 bit building working
>> while making the 64 bit changes in trunk, and still get the benefits of
>> testing. The changes involve
On 3/5/2018 8:29 AM, Patricia Shanahan wrote:
>
>
> On 3/4/2018 11:27 PM, Damjan Jovanovic wrote:
> ...
>> But there is a simple way to both keep the 64->32 bit building working
>> while making the 64 bit changes in trunk, and still get the benefits of
>> testing. The changes involved to enable t
Hi Damjan;
I personally think it would be better to start by upgrading MSVC, but in
any case...
Here are some hints from LibreOffice:
http://tml-blog.blogspot.com.co/2011/03/
Cheers,
Pedro.
-
To unsubscribe, e-mail: dev-un
On 3/4/2018 11:27 PM, Damjan Jovanovic wrote:
...
But there is a simple way to both keep the 64->32 bit building working
while making the 64 bit changes in trunk, and still get the benefits of
testing. The changes involved to enable the 64 bit build environment amount
to 1 relatively small patc
If important contributors like Patricia are going to stop contributing in
the interim if the 64->32 bit cross compiling goes away, then it's a bad
idea.
If I do the work in a separate branch, we lose the benefit of broader
testing of the 32 bit build with the changes during the port, and could
hav
On 3/4/2018 7:41 PM, Damjan Jovanovic wrote:
...
While the progress I've made [in 1 weekend ;-)] is impressive, I imagine a
full port to Win64 will be long (assembly language development for the
Win64 UNO bridge, code audit for long <-> pointer conversions which work on
*nix64 but not on Win64),
Hi
I've begun the long overdue task of porting AOO to 64 bit Windows.
With my changes so far, oowintool can now detect (the 64 bit only) Java
1.9, dmake can now compile in Cygwin64, ./configure and ./bootstrap
complete successfully, and (with uncommitted patches) both dmake and gbuild
modules man
20 matches
Mail list logo