Re: Win64 port started, and how building 32 bit AOO on Win64 could break soon
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. This will make testing AOO64 by others easier, testing AOO32 by me easier, and lead to less conflicts with other changes on affected build files. I almost have a patch ready that does this, and when I commit it, I'll use it to work on fixing the currently broken AOO32. Damjan On Mon, Mar 5, 2018 at 10:19 PM, Damjan Jovanovic wrote: > > > 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: English Dictionaries gives an error while attempting to download
Does anyone else have administrative access to that site? https://sourceforge.net/projects/aoo-extensions/ New extensions still can't be downloaded... Regards, Matthias Am 06.03.2018 um 16:49 schrieb Matthias Seidel: > Hi Dave, > > Can you please have a look? > This is not only Marco's dictionary, but also some others listed on > Twitter [1] during the last days. > > Regards, > Matthias > > [1] https://twitter.com/aooextensions > > > Am 06.03.2018 um 16:31 schrieb Matthias Seidel: >> I get "The "/17102/39/dict-en-20..dict-en-20180301.oxt" file could not >> be found or is not available. Please select another file." >> >> Download folder "/39" simply isn't there or it is invisible. >> >> Regards, >> >> Matthias >> >> >> Am 05.03.2018 um 17:42 schrieb Rory O'Farrell: >>> On Mon, 5 Mar 2018 16:37:52 + >>> "Marco A.G.Pinto" wrote: >>> Hello! As usual, I have updated the English Dictionaries, and it gives an error while attempting to download. Could someone take a look at the issue?: http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice Thank you! Kind regards, >Marco A.G.Pinto -- >>> For the record, the error is "502 Bad gateway" (just now tried). >>> >>> smime.p7s Description: S/MIME Cryptographic Signature
Re: English Dictionaries gives an error while attempting to download
The correct download page is https://extensions.openoffice.org/ On 03/12/2018 11:44 AM, Matthias Seidel wrote: Does anyone else have administrative access to that site? https://sourceforge.net/projects/aoo-extensions/ New extensions still can't be downloaded... Regards, Matthias Am 06.03.2018 um 16:49 schrieb Matthias Seidel: Hi Dave, Can you please have a look? This is not only Marco's dictionary, but also some others listed on Twitter [1] during the last days. Regards, Matthias [1]https://twitter.com/aooextensions Am 06.03.2018 um 16:31 schrieb Matthias Seidel: I get "The "/17102/39/dict-en-20..dict-en-20180301.oxt" file could not be found or is not available. Please select another file." Download folder "/39" simply isn't there or it is invisible. Regards, Matthias Am 05.03.2018 um 17:42 schrieb Rory O'Farrell: On Mon, 5 Mar 2018 16:37:52 + "Marco A.G.Pinto" wrote: Hello! As usual, I have updated the English Dictionaries, and it gives an error while attempting to download. Could someone take a look at the issue?: http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice Thank you! Kind regards, >Marco A.G.Pinto -- For the record, the error is "502 Bad gateway" (just now tried).
Fresh Volunteer for Converting arrays to containers conversion as a start.
Hi Patricia I have a volunteer from recruitment list that would like to become involved in our lovely project. He has C++ and java experience. He is currently building Open Office, and wanted to do bugfixig and code improvements for starters. I told him as a possible first task of your idea for the array conversion. He showed interest as to do this for a start. Do you have some time to help him getting started with this topic? That would be super cool! All te best Peter - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
blogpost (was: Re: deletion of not needed page)
Thanks Andrea, In general both, what we have to do, as to talk to our community seems to be important to do. But I am not convinced that a blogpost on gstreamer alone would be interesting to for the community. I think a blogpost about the 4.2.0 beta plans would indeed be helpfull. We could write a little bit about what people can prepare to test for, and of course mention the gstreamer update that we would like to see tested by the community. Also some regular Format as a blog posts would be nice. I think Star Citizen does a real good job in community management. We could grab some ideas from them. The next board report is sheduled in April. So we have to prepare a report anyhow soon. How about with the board report we publish a community Report, too? - It will be different of course from the board report, with more focus on community topics. We could always write what has happend in the Project. I think the different perspective could help a little the cause. For the first Community Report we could start off with the 4.2.0 beta plan, and what we want to do. What we hope for and talk about some highlights like gstreamer. We could also mention that work has been started on the win 64 transition. Opinions? On 11.03.2018 21:34, Andrea Pescetti wrote: Peter Kovacs wrote: can someone delete the page https://cwiki.apache.org/confluence/display/OOOUSERS/new+multimedia+Backend Now you can. I've just given you permission to delete pages. Wouldn't a blog post at https://blogs.apache.org/OOo/ with the good news be more useful (at the present state)? I mean: it may be important to create pages to track actions, and it makes sense that you do it. But it is even more important to publish the outcomes when we have good news for our users. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: blogpost
Peter Kovacs wrote: We could always write what has happend in the Project. I think the different perspective could help a little the cause. For the first Community Report we could start off with the 4.2.0 beta plan, and what we want to do. What we hope for and talk about some highlights like gstreamer. We could also mention that work has been started on the win 64 transition. Opinions? In general, I would prefer smaller posts. We even had weekly news at a point (I think it lasted for an embarrassing low number of weeks, like 4 weeks or so!). You can find traces in the CWiki: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=40508638 So something like a "monthly news" summarizing a month's worth of list traffic would work better. Of course, someone would need to volunteer for that... As for the format, we have a blog here and there's not much flexibility, this is what we get: https://blogs.apache.org/OOo/ Regards, Andrea. - 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
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. Oddly I think only the Windows build was affected by this. 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&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. > >> > > > > >
