Re: Win64 port started, and how building 32 bit AOO on Win64 could break soon

[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

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 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 could you have a quick look at:
> https://bz.apache.org/ooo/show_bug.cgi?id=127731
>
> Regards,
>Matthias
>
> > On Tue, Mar 13, 2018 at 3:52 PM, Matthias Seidel <
> matthias.sei...@hamburg.de
> >> wrote:
> >> 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 reverted all the changes to main/cppuhelper in r1826602 while I
> >>> investigate further. This should hopefully get AOO building again.
> >> Unfortunately not:
> >>
> >> ERROR: error 65280 occurred while making
> >> /cygdrive/e/slave14/aoo-win7/build/main/cppuhelper/source
> >>
> >> https://ci.apache.org/projects/openoffice/buildlogs/
> >> win/main/svtools/wntmsci12.pro/misc/logs/prj.txt
> >>
> >>> Oddly I think only the Windows build was affected by this.
> >> Yes, it seems to be Windows only.
> >>
> >> Regards,
> >>Matthias
> >>
> >>> Damjan
> >>>
> >>>
> >>> On Sun, Mar 11, 2018 at 10:01 PM, Matthias Seidel <
> >>> matthias.sei...@hamburg.de> wrote:
> >>>
>  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 10.03.2018 um 19:18 schrieb Matthias Seidel:
> > 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/wntmsci12.pro/misc/logs/source.txt
> > Regards,
> >
> >   Matthias
> >
> > [1] https://svn.apache.org/viewvc?view=revision=1826398
> >
> >
> > Am 05.03.2018 um 21:19 schrieb Damjan Jovanovic:
> >> 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 involved to enable the 64 bit build
> environment
>  amount
>  to 1 relatively small patch affecting only 5 files, and without
> this
>  patch
>  it will still build 32 bit binaries on 64 bit Windows. Thus this
>  patch can
>  be maintained out-of-tree while patching modules to build on
> Win64,
>  and
>  those building without this patch will end up automatically
> testing
>  whether
>  any of the (small and relatively safe) module changes broke the
> >> Win32
>  build.
> 
> >>> ...
> >>>
> >>> In general, I favor keeping things checked in, but in keep the
> patch
>  that
> >>> breaks 64->32 in its own branch. The remaining changes can go in
> the
>  trunk.
> >> The patch affects 4 files and is only 254 lines long in total, so
> I've
>  just
> >> placed it into main/solenv/win64/win64.patch together with a readme
> >> file
> >> referring people to the wiki page (
> >> https://wiki.openoffice.org/wiki/Win64_port) where I've described
> how
>  to
> >> apply it and start the Win64 build.
> >>
> 
> >>
> >>
>
>
>

Re: First steps in building with MSVC 14 / Visual Studio 2015

[Pedro Giffuni]

Hi again;

On 03/13/18 13:10, Pedro Giffuni wrote:

Hi Damjan;

Glad to see this progress! To build python with newer versions of 
MSVC, you may have to change the BUILD_DIR to "PCbuild".


Look at main/python/makefile.mk line 125.



I committed a small adjustment in r1826694, to clarify better the situation.

I don't have a way of testing the windows build so feel free to revert 
if I managed to break things in some spectacular way :-/.


Cheers,

Pedro.


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

Re: Win64 port started, and how building 32 bit AOO on Win64 could break soon

[Matthias Seidel]

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 could you have a quick look at:
https://bz.apache.org/ooo/show_bug.cgi?id=127731

Regards,
   Matthias

> 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 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
>>> investigate further. This should hopefully get AOO building again.
>> Unfortunately not:
>>
>> ERROR: error 65280 occurred while making
>> /cygdrive/e/slave14/aoo-win7/build/main/cppuhelper/source
>>
>> https://ci.apache.org/projects/openoffice/buildlogs/
>> win/main/svtools/wntmsci12.pro/misc/logs/prj.txt
>>
>>> Oddly I think only the Windows build was affected by this.
>> Yes, it seems to be Windows only.
>>
>> Regards,
>>Matthias
>>
>>> Damjan
>>>
>>>
>>> On Sun, Mar 11, 2018 at 10:01 PM, Matthias Seidel <
>>> matthias.sei...@hamburg.de> wrote:
>>>
 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 10.03.2018 um 19:18 schrieb Matthias Seidel:
> 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/wntmsci12.pro/misc/logs/source.txt
> Regards,
>
>   Matthias
>
> [1] https://svn.apache.org/viewvc?view=revision=1826398
>
>
> Am 05.03.2018 um 21:19 schrieb Damjan Jovanovic:
>> 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 involved to enable the 64 bit build environment
 amount
 to 1 relatively small patch affecting only 5 files, and without this
 patch
 it will still build 32 bit binaries on 64 bit Windows. Thus this
 patch can
 be maintained out-of-tree while patching modules to build on Win64,
 and
 those building without this patch will end up automatically testing
 whether
 any of the (small and relatively safe) module changes broke the
>> Win32
 build.

>>> ...
>>>
>>> In general, I favor keeping things checked in, but in keep the patch
 that
>>> breaks 64->32 in its own branch. The remaining changes can go in the
 trunk.
>> The patch affects 4 files and is only 254 lines long in total, so I've
 just
>> placed it into main/solenv/win64/win64.patch together with a readme
>> file
>> referring people to the wiki page (
>> https://wiki.openoffice.org/wiki/Win64_port) where I've described how
 to
>> apply it and start the Win64 build.
>>

>>
>>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: First steps in building with MSVC 14 / Visual Studio 2015

[Matthias Seidel]

Hi Damjan,

Am 13.03.2018 um 18:15 schrieb Damjan Jovanovic:
> I used Cygwin64 but did a 32 bit AOO build. (You can do that now; my 64 bit
> patches fixed the issues we had with Cygwin64 before.)

I will try that later, I would love to go to Cygwin64 for all my builds...

If it works, we can finally update the MWiki section for Cygwin64:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Testing_build_with_Cygwin_64_bit

Regards,
   Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Missing Release/Tag for AOO415 on GitHub

[Matthias Seidel]

Am 13.03.2018 um 21:18 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> Just for the record, the release/tag for AOO 4.1.5 is missing on GitHub:
>> https://github.com/apache/openoffice/releases
>> @Jim: Can you add it like you did for 4.1.4?
>
> We shouldn't tag in Github. Github does not exist as an official
> repository.
>
> Tags go here:
> https://svn.apache.org/viewvc/openoffice/tags/
> and Github will pick it up from there once it is added.

If it works this way, I am perfectly OK with it. ;-)
(I was *really* under the impression that we had a 415 tag in SVN but
not on GitHub, should have looked before writing...)

Regards,
   Matthias

>
> Github is a mirror when it works, a nuisance when it doesn't (but it
> looks like the mirror mechanism was fixed recently).
>
> Regards,
>   Andrea.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Missing Release/Tag for AOO415 on GitHub

[Andrea Pescetti]

Matthias Seidel wrote:

Just for the record, the release/tag for AOO 4.1.5 is missing on GitHub:
https://github.com/apache/openoffice/releases
@Jim: Can you add it like you did for 4.1.4?


We shouldn't tag in Github. Github does not exist as an official repository.

Tags go here:
https://svn.apache.org/viewvc/openoffice/tags/
and Github will pick it up from there once it is added.

Github is a mirror when it works, a nuisance when it doesn't (but it 
looks like the mirror mechanism was fixed recently).


Regards,
  Andrea.

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

Re: Openoffice and unsupported gstreamer 0.10 branch (for openoffice libavmediagst.so library)

[Torokhov Sergey]

It's a great news! 
I shall look forward to preliminary AOO 4.2.0 builds to test new
gstreamer-1.0 implementation.

--
Sergey


On Fri, 2 Mar 2018 08:14:44 +0200
Damjan Jovanovic  wrote:

> I finally cracked it. The gstreamer pipeline gets created early,
> during construction of the avmedia/source/gstreamer's Player object,
> yet the window to play in is only created later, when
> createPlayerWindow() is called. To use that window and thus embed
> video into the document, we have to set that window's handle to the
> GstVideoOverlay using gst_video_overlay_set_window_handle(), but by
> then it's too late. Either the pipeline creation would have to be
> deferred until createPlayerWindow(), when we know the window to use,
> or we would have to switch windows with
> gst_video_overlay_set_window_handle() a live pipeline. I've done the
> latter and it works well. I don't know how it ever worked before,
> maybe in gstreamer 0.1 the "prepare-window-handle" event is generated
> during createPlayerWindow() but in 1.0 it isn't.
> 
> My changes have been committed to SVN trunk in revision 1825700.
> 
> Torokhov, Jose, Peter: thank you for all your support. Please test and
> report any problems.
> 
> Damjan





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

Re: Treffen in Berlin (war: Re: https://www.heise.de/ix/meldung/Apache-Konferenz-kommt-nach-Berlin-3953326.html)

[Matthias Seidel]

Am 13.03.2018 um 20:15 schrieb Jörg Schmidt:
> Hallo Mathias, 
>
>> -Original Message-
>> From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] 
>> Sent: Tuesday, March 13, 2018 5:12 PM
>> To: dev-de@openoffice.apache.org
>> Subject: Treffen in Berlin (war: Re: 
>> https://www.heise.de/ix/meldung/Apache-Konferenz-kommt-nach-Be
>> rlin-3953326.html)
>> Das Hotel ist gebucht, vielleicht könnten wir uns an dem 
>> Sonntag treffen?
> Ja, das können wir gerne tun. 
>
> Kannst Du mich bitte ca. eine Woche vor dem Termin nochmal kontakten, damit 
> wir die genaue Zeit/Ort absprechen können? 

Gerne, der genaue Tagesablauf ist mir auch noch nicht bekannt. ;-)

Gruß, Matthias

>
>
>> [1] https://www.warpstock.eu/2018/42-warpstock-europe-2018-in-berlin
> Das Hotel ist mir bekannt, weil ich häufiger daran vorbeifahre.
>
>
>
> Gruß
> Jörg
>
>
> -
> To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-de-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Treffen in Berlin (war: Re: https://www.heise.de/ix/meldung/Apache-Konferenz-kommt-nach-Berlin-3953326.html)

[Jörg Schmidt]

Hallo Mathias, 

> -Original Message-
> From: Matthias Seidel [mailto:matthias.sei...@hamburg.de] 
> Sent: Tuesday, March 13, 2018 5:12 PM
> To: dev-de@openoffice.apache.org
> Subject: Treffen in Berlin (war: Re: 
> https://www.heise.de/ix/meldung/Apache-Konferenz-kommt-nach-Be
> rlin-3953326.html)

> Das Hotel ist gebucht, vielleicht könnten wir uns an dem 
> Sonntag treffen?

Ja, das können wir gerne tun. 

Kannst Du mich bitte ca. eine Woche vor dem Termin nochmal kontakten, damit wir 
die genaue Zeit/Ort absprechen können? 


> [1] https://www.warpstock.eu/2018/42-warpstock-europe-2018-in-berlin

Das Hotel ist mir bekannt, weil ich häufiger daran vorbeifahre.



Gruß
Jörg


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

Missing Release/Tag for AOO415 on GitHub

[Matthias Seidel]

Just for the record, the release/tag for AOO 4.1.5 is missing on GitHub:
https://github.com/apache/openoffice/releases

@Jim: Can you add it like you did for 4.1.4?

Regards, Matthias




smime.p7s
Description: S/MIME Cryptographic Signature

Re: First steps in building with MSVC 14 / Visual Studio 2015

[Pedro Giffuni]

Hi Damjan;

Glad to see this progress! To build python with newer versions of MSVC, 
you may have to change the BUILD_DIR to "PCbuild".


Look at main/python/makefile.mk line 125.

Cheers,

Pedro.

ps. As a reminder, the ASF has access to MSDN in case someone wants to help.


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

First steps in building with MSVC 14 / Visual Studio 2015

[Damjan Jovanovic]

Hi

I am not just working on the Win64 port, but also had a brief look at
building AOO with the newer MSVC 14 in Visual Studio 2015.

I used Cygwin64 but did a 32 bit AOO build. (You can do that now; my 64 bit
patches fixed the issues we had with Cygwin64 before.)

First step was patching oowintool to detect the new MSVC, by adding its
registry keys, but that wasn't sufficient and I had to use
--with-frame-home, --with-psdk-home, and co. I discovered I have different
MSVC registry keys for 32 bit and 64 bit; oowintool currently looks at the
current bitness keys first and on Cygwin64 falls back to 32 bit keys if
missing, but I think it needs to only look at keys in the AOO bitness.

Then oowintool is called to copy CRT files from MSVC, and needed more
patching copy the right files, with the new version numbers.

It turns out as of MSVC 14, Microsoft requires us link each binary with a
total of 4 C/C++ runtime libraries (https://docs.microsoft.com/en
-us/cpp/c-runtime-library/crt-library-features): the old MSVCRT.LIB which
has now become a CRT initialization library, the old MSVCPRT.LIB which
implements the C++ standard library, the new UCRT.LIB which is their new
C99 standard library, and the new VCRUNTIME.LIB which deals with exception
handling, RTTI and debugging. I guess the small mercy is that we would only
gain runtime dependencies on UCRTBASE.DLL and VCRUNTIME.DLL, the
other 2 are statically linked. I hacked our dmake makefiles to link with
the new libraries by default. We'll also need to update our installer to
install the redistributable versions of these DLLs.

It also turns out that there is now this new Windows development component,
the "Windows Kit" under C:\Program Files (x86)\Windows Kits\, that
you have to use, which contains the C standard header files and UCRT.LIB. I
had to hack SOLARINC and ILIB in my winenv.set.sh to add those, but we
should do that better somehow.

Anyway with those changes the build started. It successfully built a few
modules including ext_libraries/apr, then broke in main/solenv due to
PATH_MAX no longer existing in limits.h, but when I patched that, it
compiled and linked the solenv tools successfully. It broke further, in
ext_libraries/gtest, due to C++ template issues that don't seem easy to
fix. Maybe a newer version of Google Test would help; for now
--disable-unit-tests got me further, then it broke in main/python, which I
am now stuck at.

I don't think porting our code to use MSVC 14 will be that difficult. It
looks like just a few issues at the module level. Python may be hard to
fix, as it is fussy about the CRT libraries (the Python documentation says
it requires MSVCP90).

The patches need refinement before being committed. These "Windows Kits"
needs further research. Also would anyone be interested in helping?

Damjan

Re: Win64 port started, and how building 32 bit AOO on Win64 could break soon

[Damjan Jovanovic]

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 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
> > investigate further. This should hopefully get AOO building again.
>
> Unfortunately not:
>
> ERROR: error 65280 occurred while making
> /cygdrive/e/slave14/aoo-win7/build/main/cppuhelper/source
>
> https://ci.apache.org/projects/openoffice/buildlogs/
> win/main/svtools/wntmsci12.pro/misc/logs/prj.txt
>
> >
> > Oddly I think only the Windows build was affected by this.
>
> Yes, it seems to be Windows only.
>
> Regards,
>Matthias
>
> >
> > Damjan
> >
> >
> > On Sun, Mar 11, 2018 at 10:01 PM, Matthias Seidel <
> > matthias.sei...@hamburg.de> wrote:
> >
> >> 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 10.03.2018 um 19:18 schrieb Matthias Seidel:
> >>> 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/wntmsci12.pro/misc/logs/source.txt
> >>> Regards,
> >>>
> >>>   Matthias
> >>>
> >>> [1] https://svn.apache.org/viewvc?view=revision=1826398
> >>>
> >>>
> >>> Am 05.03.2018 um 21:19 schrieb Damjan Jovanovic:
>  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 involved to enable the 64 bit build environment
> >> amount
> >> to 1 relatively small patch affecting only 5 files, and without this
> >> patch
> >> it will still build 32 bit binaries on 64 bit Windows. Thus this
> >> patch can
> >> be maintained out-of-tree while patching modules to build on Win64,
> >> and
> >> those building without this patch will end up automatically testing
> >> whether
> >> any of the (small and relatively safe) module changes broke the
> Win32
> >> build.
> >>
> > ...
> >
> > In general, I favor keeping things checked in, but in keep the patch
> >> that
> > breaks 64->32 in its own branch. The remaining changes can go in the
> >> trunk.
> >
>  The patch affects 4 files and is only 254 lines long in total, so I've
> >> just
>  placed it into main/solenv/win64/win64.patch together with a readme
> file
>  referring people to the wiki page (
>  https://wiki.openoffice.org/wiki/Win64_port) where I've described how
> >> to
>  apply it and start the Win64 build.
> 
> >>
> >>
>
>
>

Re: Win64 port started, and how building 32 bit AOO on Win64 could break soon

[Matthias Seidel]

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 reverted all the changes to main/cppuhelper in r1826602 while I
> investigate further. This should hopefully get AOO building again.

Unfortunately not:

ERROR: error 65280 occurred while making
/cygdrive/e/slave14/aoo-win7/build/main/cppuhelper/source

https://ci.apache.org/projects/openoffice/buildlogs/win/main/svtools/wntmsci12.pro/misc/logs/prj.txt

>
> Oddly I think only the Windows build was affected by this.

Yes, it seems to be Windows only.

Regards,
   Matthias

>
> Damjan
>
>
> On Sun, Mar 11, 2018 at 10:01 PM, Matthias Seidel <
> matthias.sei...@hamburg.de> wrote:
>
>> 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 10.03.2018 um 19:18 schrieb Matthias Seidel:
>>> 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/wntmsci12.pro/misc/logs/source.txt
>>> Regards,
>>>
>>>   Matthias
>>>
>>> [1] https://svn.apache.org/viewvc?view=revision=1826398
>>>
>>>
>>> Am 05.03.2018 um 21:19 schrieb Damjan Jovanovic:
 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 involved to enable the 64 bit build environment
>> amount
>> to 1 relatively small patch affecting only 5 files, and without this
>> patch
>> it will still build 32 bit binaries on 64 bit Windows. Thus this
>> patch can
>> be maintained out-of-tree while patching modules to build on Win64,
>> and
>> those building without this patch will end up automatically testing
>> whether
>> any of the (small and relatively safe) module changes broke the Win32
>> build.
>>
> ...
>
> In general, I favor keeping things checked in, but in keep the patch
>> that
> breaks 64->32 in its own branch. The remaining changes can go in the
>> trunk.
>
 The patch affects 4 files and is only 254 lines long in total, so I've
>> just
 placed it into main/solenv/win64/win64.patch together with a readme file
 referring people to the wiki page (
 https://wiki.openoffice.org/wiki/Win64_port) where I've described how
>> to
 apply it and start the Win64 build.

>>
>>




smime.p7s
Description: S/MIME Cryptographic Signature

Treffen in Berlin (war: Re: https://www.heise.de/ix/meldung/Apache-Konferenz-kommt-nach-Berlin-3953326.html)

[Matthias Seidel]

Hallo Jörg,

Am 02.02.2018 um 07:15 schrieb Jörg Schmidt:
>
>> Gerne, allerdings steht außer dem Termin noch nichts genaues. 
>> Werde aber
>> wohl Samstag bis Sonntag da sein, da findet sich bestimmt eine
>> Möglichkeit...
> Melde Dich einfach sobald Du Dir im Klaren über den Termin bist.

Also, der Termin steht [1]: 26. bis 27. Mai

Das Hotel ist gebucht, vielleicht könnten wir uns an dem Sonntag treffen?

Gruß, Matthias

[1] https://www.warpstock.eu/2018/42-warpstock-europe-2018-in-berlin

>
> ich kann normalerweise auch kurzfristig, dazwischenkomen kann immer etwas, 
> aber das sehen wir dann
>
>
>
> Gruß
> Jörg
>
>
> -
> To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-de-h...@openoffice.apache.org
>




smime.p7s
Description: S/MIME Cryptographic Signature