Great!
My build just finished. I successfully tested the "shellext"
functionality on Windows 10 64bit.
@Jim:
Maybe we can integrate Dons latest expat patch in 4.1.4, so we can have
a test version available from our buildbot?
http://svn.apache.org/viewvc?view=revision&revision=1805208
Also we coul
Yes it did.
On 19 Aug, Matthias Seidel wrote:
> Hi Don,
>
> Did 4.1.4 build and work with your patch?
>
> Matthias
>
>
> Am 16.08.2017 um 21:34 schrieb Don Lewis:
>> On 16 Aug, Matthias Seidel wrote:
>>> Am 16.08.2017 um 19:51 schrieb Don Lewis:
I fixed the --enable-win-x64-shellext probl
Hi Don,
Did 4.1.4 build and work with your patch?
Matthias
Am 16.08.2017 um 21:34 schrieb Don Lewis:
> On 16 Aug, Matthias Seidel wrote:
>> Am 16.08.2017 um 19:51 schrieb Don Lewis:
>>> I fixed the --enable-win-x64-shellext problem in r1805208.
>> Great!
>> Now we could have all Windows buildbo
On 16 Aug, Matthias Seidel wrote:
> Am 16.08.2017 um 19:51 schrieb Don Lewis:
>> I fixed the --enable-win-x64-shellext problem in r1805208.
>
> Great!
> Now we could have all Windows buildbots in release quality!
> (If they were only functional and Infra would assign my ticket...)
>
> BTW: Should
Am 16.08.2017 um 19:51 schrieb Don Lewis:
> I fixed the --enable-win-x64-shellext problem in r1805208.
Great!
Now we could have all Windows buildbots in release quality!
(If they were only functional and Infra would assign my ticket...)
BTW: Should we backport r1805208 to 4.1.4?
>
> On 16 Aug, M
I fixed the --enable-win-x64-shellext problem in r1805208.
On 16 Aug, Matthias Seidel wrote:
> Hi Don,
>
> it worked like a charm! ;-)
>
> My first AOO 4.2.0 builds are to be found here:
> https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/
>
> My next build will be with "--enable-win-x64
Hi Don,
it worked like a charm! ;-)
My first AOO 4.2.0 builds are to be found here:
https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/
My next build will be with "--enable-win-x64-shellext" but I suspect it
will stop because of expat2.2.3.
(For 4.1.4 we reverted to Jims patch)
Matthias
On 15 Aug, Matthias Seidel wrote:
> Am 15.08.2017 um 11:18 schrieb Don Lewis:
>> On 10 Aug, Matthias Seidel wrote:
>>> I could now get past the gtest error by disabling unit tests
>>> (--disable-unit-tests).
>>>
>>> Errors in udm and xml2cmp remain:
>>>
>>> make: *** No rule to make target
>>> '/c
Am 15.08.2017 um 11:18 schrieb Don Lewis:
> On 10 Aug, Matthias Seidel wrote:
>> I could now get past the gtest error by disabling unit tests
>> (--disable-unit-tests).
>>
>> Errors in udm and xml2cmp remain:
>>
>> make: *** No rule to make target
>> '/cygdrive/e/slave14/aoo-win7/build/main/udm/so
On 15 Aug, Matthias Seidel wrote:
> Am 14.08.2017 um 03:20 schrieb Damjan Jovanovic:
>> On Sun, Aug 13, 2017 at 10:57 PM, Matthias Seidel <
>> matthias.sei...@hamburg.de> wrote:
>>
>>> Am 13.08.2017 um 10:57 schrieb Damjan Jovanovic:
>>>
>>> :(.
>>>
>>> gmake version?
>>>
>>> ---
>>> $ gmake
>>> -b
.h
>>
>> dmake: Error code 2, while making './wntmsci12.pro/misc/build/
>>
>> so_built_oo_gtest'
>>
>> 1 module(s):
>> gtest
>> need(s) to be rebuilt
>>
>> Reason(s):
>>
>> ERROR: error 65280 occurred w
On 10 Aug, Matthias Seidel wrote:
> I could now get past the gtest error by disabling unit tests
> (--disable-unit-tests).
>
> Errors in udm and xml2cmp remain:
>
> make: *** No rule to make target
> '/cygdrive/e/slave14/aoo-win7/build/main/udm/source/inc/precomp.h
> ', needed by
> '/cygdrive/e
Making:all_salhelper.dpslo
> Compiling: salhelper/wntmsci12.pro/misc/salhelper3MSC_version.c
> Compiling: salhelper/source/condition.cxx
> ../inc\salhelper/condition.hxx(29) : fatal error C1083: Cannot
>
> open include file: 'osl/conditn.h': No such file or directory
>
e 2, while making './wntmsci12.pro/misc/build/
>> so_built_oo_gtest'
>>>>>>>> 1 module(s):
>>>>>>>> gtest
>>>>>>>> need(s) to be rebuilt
>>>>>>>>
>>>>>>>> R
fixed the errors in that module you can resume the
> build by running:
> >>>>>>
> >>>>>> build --all:gtest
> >>>>>>
> >>>>>> The sal helper cannot open include file conditn.h
> >>>>>>
>
>>> /cygdrive/c/source/aoo-trunk/ext_libraries/gtest
>>>>>>
>>>>>> When you have fixed the errors in that module you can resume the build
>>>>>> by running:
>>>>>>
>>>>>> build --all:gtest
>>>>>&g
>
>>>>> build --all:gtest
>>>>>
>>>>> The sal helper cannot open include file conditn.h
>>>>>
>>>>> =
>>>>> Building module salhelper
>>>>> =
>>>>>
>>
=
>>>> Building module salhelper
>>>> =
>>>>
>>>> Entering /cygdrive/c/source/aoo-trunk/main/salhelper/source
>>>>
>>>> mkout -- version: 1.8
>>>> Making:all_salhelper.dpslo
>>>> Com
le: 'osl/conditn.h': No such file or directory
>>> dmake: Error code 2, while making '../wntmsci12.pro/slo/condition.obj'
>>>
>>> 1 module(s):
>>> salhelper
>>> need(s) to be rebuilt
>>>
>>> Reason(s):
>
2.pro/slo/condition.obj'
>>
>> 1 module(s):
>> salhelper
>> need(s) to be rebuilt
>>
>> Reason(s):
>>
>> ERROR: error 65280 occurred while making
>> /cygdrive/c/source/aoo-trunk/main/salhelper/source
>>
>> When you have fixe
(s) to be rebuilt
>
> Reason(s):
>
> ERROR: error 65280 occurred while making
> /cygdrive/c/source/aoo-trunk/main/salhelper/source
>
> When you have fixed the errors in that module you can resume the build by
> running:
>
> build --all:salhelper
>
>
>
>> >
>> I agree. The wiki did say they managed to open all of AOO in one
>Eclipse
>> project, but it took a lot of memory. I must try it some time.
>>
>
>You can open AOO in ONE Eclipse project but it does take a lot of
>physical
>memory. And you need to up the memory for your Java considerably
IDE support.
> > >>> I would like to use intelliJ, but the IDE does not support java and
> > >C/C++
> > >>> at the same time. However a feature request has been made, and the
> > >creator
> > >>> company plans the support somewhere
r directory
dmake: Error code 2, while making
'../wntmsci12.pro/slo/condition.obj
'
1 module(s):
salhelper
need(s) to be rebuilt
Reason(s):
ERROR: error 65280 occurred while making
/cygdrive/c/source/aoo-trunk/
main/salhelper/source
When you have fixed the errors in that m
;>> gb_Deliver_deliver: file does not exist in solver, and cannot be
>>>>> deli.
>>>>> Stop.nk/main/solver/420/wntmsci12.pro/inc/gtest/gtest.h
>>>>>> dmake: Error code 2, while making './wntmsci12.pro/misc/build/
>>>>> so_built_oo_gte
main/salhelper/source
When you have fixed the errors in that module you can resume the build
by running:
build --all:salhelper
From: Yemelyanenko Fyodor [mailto:fyodo...@hotmail.com]
Sent: Wednesday, July 19, 2017 10:51 AM
To: Damjan Jovanovic ; Apache OO <
dev@openoffice.apache.org&g
think I misconfigured some prerequisite, and this is not error in code.
-Original Message-
From: Damjan Jovanovic [mailto:dam...@apache.org]
Sent: Thursday, July 20, 2017 8:35 PM
To: Apache OO
Subject: Re: Building OO
Hi Matthias
As I posted earlier in this thread, this is how I build it:
32
en include file conditn.h
> >>>
> >>> =
> >>> Building module salhelper
> >>> =
> >>>
> >>> Entering /cygdrive/c/source/aoo-trunk/main/salhelper/source
> >>>
> >>> mkout -- version:
hxx(29) : fatal error C1083: Cannot open
>> include file: 'osl/conditn.h': No such file or directory
>>> dmake: Error code 2, while making '../wntmsci12.pro/slo/condition.obj'
>>>
>>> 1 module(s):
>>> salhelper
>>> ne
t; need(s) to be rebuilt
> >
> > Reason(s):
> >
> > ERROR: error 65280 occurred while making /cygdrive/c/source/aoo-trunk/
> main/salhelper/source
> >
> > When you have fixed the errors in that module you can resume the build
> by running:
> >
> >
o-trunk/main/salhelper/source
>
> When you have fixed the errors in that module you can resume the build by
> running:
>
> build --all:salhelper
>
>
>
> From: Yemelyanenko Fyodor [mailto:fyodo...@hotmail.com]
> Sent: Wednesday, July 19, 2017 10:51 AM
>
lhelper/source
>
>When you have fixed the errors in that module you can resume the build
>by running:
>
>build --all:salhelper
>
>
>
>From: Yemelyanenko Fyodor [mailto:fyodo...@hotmail.com]
>Sent: Wednesday, July 19, 2017 10:51 AM
>To: Damjan Jovanovic ; Apac
jan Jovanovic ; Apache OO
Subject: Re[5]: Building OO
Hello!
I've switched to Ubuntu 14.04 mini with xubuntu-desktop and xrdp installed
And OO built successfully! :-)
Now trying to do the same on W7 x32.
As Id like to deep dive into OO development, could you please share what dev
environm
basic IDE support.
>> >>> I would like to use intelliJ, but the IDE does not support java
>and
>> >C/C++
>> >>> at the same time. However a feature request has been made, and
>the
>> >creator
>> >>> company plans the support somewhere i
Hi all
Long time ago, most IDE faild with the size of the OO Code. I also know,
that XCode failed. But I think, Time has changed. We have more RAM now. In
NetBeans you have probably to extend the RAM in the JVM. I never tryed it.
but I think I will. It will be interesting for testing. And i
About 5 years ago, when I tried to used Netbeans to open a large C project
(the Wine project, about 2 million lines), it was unusably slow, and its
C/C++ indexer crashed.
I don't know if it has improved since then, but we have 6 times more code,
and it's C++, not the much simpler C. Eclipse invest
yodor
:
Yes, sure, I mean IDE
-- Исходное сообщение --
От: "Peter Kovacs"
Кому: dev@openoffice.apache.org
Отправлено: 19.07.2017 14:51:57
Тема: Re: Re[5]: Building OO
Hello,
Do you mean by dev environment an IDE?
All the best
Peter
Am 19. Juli 2017 02:50:48 MESZ schrieb Yeme
ed to hopp at Eclipse, since it has the best support
> >today. I am
> >>> thinking about a special IDE plugin. But I have not made much
> >progress.
> >>> Still bound to vi and command-line.
> >>>
> >>> Patricia is using Visual Studio
On 7/19/17, Damjan Jovanovic wrote:
> What is so "very basic" about Eclipse? It's an excellent IDE, among the
> best C++ IDEs I ever used, and the only IDE I use to develop AOO.
>
> I only used Visual Studio a little, and it seemed very good at the .NET
> languages, but poor at C++. What does Visu
cial IDE plugin. But I have not made much
>progress.
>>> Still bound to vi and command-line.
>>>
>>> Patricia is using Visual Studio on Windows I think. How is it
>helping?
>>>
>>> All the best
>>> Peter
>>>
>>> Am 19. Juli 2017
2 MESZ schrieb Yemelyanenko Fyodor <
>> fyodo...@hotmail.com>:
>>> Yes, sure, I mean IDE
>>>
>>> -- Исходное сообщение --
>>> От: "Peter Kovacs"
>>> Кому: dev@openoffice.apache.org
>>> Отправлено: 19.07.2017 14:51:5
g?
>
> All the best
> Peter
>
> Am 19. Juli 2017 07:35:42 MESZ schrieb Yemelyanenko Fyodor <
> fyodo...@hotmail.com>:
> >Yes, sure, I mean IDE
> >
> >-- Исходное сообщение --
> >От: "Peter Kovacs"
> >Кому: dev@openoffice.apach
--
>От: "Peter Kovacs"
>Кому: dev@openoffice.apache.org
>Отправлено: 19.07.2017 14:51:57
>Тема: Re: Re[5]: Building OO
>
>>Hello,
>>
>>Do you mean by dev environment an IDE?
>>
>>All the best
>>Peter
>>
>>Am 19. Juli 2017 02:
Yes, sure, I mean IDE
-- Исходное сообщение --
От: "Peter Kovacs"
Кому: dev@openoffice.apache.org
Отправлено: 19.07.2017 14:51:57
Тема: Re: Re[5]: Building OO
>Hello,
>
>Do you mean by dev environment an IDE?
>
>All the best
>Peter
>
>Am 19. Juli 2017
e same on W7 x32.
>
>As Id like to deep dive into OO development, could you please share
>what dev environment do you use on Ubuntu and on W7 (I believe, that
>I'll finally success in building OO on Windows).
>Any thoughts on establishing dev environment will be appreciat
I'll finally
success in building OO on Windows).
Any thoughts on establishing dev environment will be appreciated.
--
Fyodor
-- Исходное сообщение --
От: "Емельяненко Федор" mailto:fyodo...@hotmail.com>>
Кому: "Damjan Jovanovic" mailto:dam...@apache
hat module you can resume the build by
running:
build --all:gtest
-- Исходное сообщение ------
От: "Damjan Jovanovic" mailto:dam...@apache.org>>
Кому: "Yemelyanenko Fyodor" mailto:fyodo...@hotmail.com>>
Копия: "Apache OO" mailto:dev@openoffice.apache.org&
>
> ERROR: error 65280 occurred while making
> /cygdrive/c/source/aoo-trunk/main/xml2cmp/prj
>
> When you have fixed the errors in that module you
> can resume the
> build by running:
>
> build
build --all:xml2cmp
-- Исходное сообщение --
От: "Damjan Jovanovic"
Кому: "Yemelyanenko Fyodor"
Копия: "Apache OO"
Отправлено: 28.06.2017 15:07:29
Тема: Re: Building OO
>Hi Fyodor
>
>The problem is almost certainly in
&g
;ll
appreciate reference to information on dmake.
--
Fyodor
From: Damjan Jovanovic [mailto:dam...@apache.org]
Sent: Tuesday, June 27, 2017 5:38 PM
To: Apache OO ; fyodo...@hotmail.com
Subject: Re: Building OO
Hi Fyodor
Welcome to AOO :).
What version are you building?
Can you "cd" into
;ll be able to trace build
> and link processes and find what exactly done on udm module. So I'll
> appreciate reference to information on dmake.
>
> --
> Fyodor
>
>
> From: Damjan Jovanovic [mailto:dam...@apache.org]
> Sent: Tuesday, June 27, 2017 5:38 PM
> To: Apa
Hi Fyodor,
I think I had the same Issue when trying to build 4.2.0 (trunk).
But then I concentrated on 4.1.4 and did successful build with Java 1.7
and Ant 1.9.9.
Kind regards, Matthias
Am 27.06.2017 um 08:12 schrieb Yemelyanenko Fyodor:
> =
> Building module udm
> =
>
Hi Fyodor
Welcome to AOO :).
What version are you building?
Can you "cd" into the udm directory, and post the full output of "build"
run from there?
Thank you
Damjan
On Tue, Jun 27, 2017 at 8:12 AM, Yemelyanenko Fyodor
wrote:
> =
> Building module udm
> =
>
> Entering
=
Building module udm
=
Entering /cygdrive/c/source/aoo-trunk/main/udm/prj
Hello!
I'm newbie in OO development, and as New Volunteer Orientation module suggests,
I've established local build env, and try to build OO.
I've installed required prerequisites from Building Gui
Hi Pavel,
Did you update the wiki accordingly?
If you don't have a MediaWiki (MWiki) account, you can request one...
Regards, Matthias
Am 03.05.2017 um 00:47 schrieb Pavel Belski:
> I tried to build OpenOffice from svn's AOO413 tag today, this time
> successful.
>
> Still i have to say that th
Hi Pavel,
That sounds great!
I did also finish my first build on Windows.
According to your mail I took Java 1.7. Additionally I added German
language and enabled dictionaries...
Regards, Matthias
Am 06.05.2017 um 09:40 schrieb Pavel Belski:
> The 4.1.4 branch built normally
>
> 2017-05-05 17:
That is exceptionally good news!
> On May 6, 2017, at 3:40 AM, Pavel Belski wrote:
>
> The 4.1.4 branch built normally
>
> 2017-05-05 17:24 GMT+02:00 Pavel Belski :
>
>> Building the current revision of 4.1.4 right now, it will take several
>> hours but for now it's looking good.
>> I will inf
The 4.1.4 branch built normally
2017-05-05 17:24 GMT+02:00 Pavel Belski :
> Building the current revision of 4.1.4 right now, it will take several
> hours but for now it's looking good.
> I will inform you as soon as it is ready
>
> 2017-05-04 19:17 GMT+02:00 Matthias Seidel :
>
>> Hi Pavel,
>>
>
Building the current revision of 4.1.4 right now, it will take several
hours but for now it's looking good.
I will inform you as soon as it is ready
2017-05-04 19:17 GMT+02:00 Matthias Seidel :
> Hi Pavel,
>
> I encountered exactly the same error in trunk but didn't go further on.
> Perhaps it is
Hi Pavel,
I encountered exactly the same error in trunk but didn't go further on.
Perhaps it is related to the changes regarding gbuild?
Maybe you want to give the 4.1.4 branch a try?
https://svn.apache.org/repos/asf/openoffice/branches/AOO414/
Regards, Matthias
Am 01.05.2017 um 13:50 schrieb
I tried to build OpenOffice from svn's AOO413 tag today, this time
successful.
Still i have to say that the wiki page with step-by-step guide has some
errors that i had to deal with(or it's outdated a bit).
Things that I encountered so far:
1. Suggested ./configure option list in the wiki is miss
Hi all,
currently i'm trying to build Open Office from svn sources, closely
following the guide in
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1.2C_Windows_10.
The trunk revision i currently have is
Pavel@Pavel-PC /cygdrive/c/oosources/aoo
On 17/02/2013 cguerber wrote:
I'm new here and am interested in doing some bug fixing proposals if
I can.
Welcome, Christophe! I see you are still waiting for an answer.
So I tried to build OO on my new VM with a Debian. All went quite
well until today: when I build OO, it creates "linux-2.6-
63 matches
Mail list logo
