Re: Build r1829228 on Linux-32 (gstreamer build problem)

On 1 May, Peter kovacs wrote: > I think we do have the pain only with Linux. Since some distributions > move slower then others. > > We could bundle the only 1.0.0 with Windows and Mac I think. For Linux > we would need some logic, that identifies the right gstreamer > available on the distributi

Re: Build r1829228 on Linux-32 (gstreamer build problem)

​Thanks for this info, Damjan. It would be very useful if we could identify the Linux media player that would likely be used -- as DirectX is for WNT and QuickTime for Mac. Maybe VLC? This would mean defining a new ​AVMEDIA_MANAGER_SERVICE_NAME, right? On Tue, May 1, 2018 at 6:51 AM, Damjan Jovan

Re: Build r1829228 on Linux-32 (gstreamer build problem)

In main/avmedia/source/inc/mediamisc.hxx, the media player is chosen with the following code. Note how GStreamer is only used on non-Windows non-Mac platforms. #ifdef WNT #define AVMEDIA_MANAGER_SERVICE_NAME "com.sun.star.comp.avmedia.Manager_DirectX" #define AVMEDIA_MANAGER_SERVICE_IS_JAVABASED

Re: Build r1829228 on Linux-32 (gstreamer build problem)

I think we do have the pain only with Linux. Since some distributions move slower then others. We could bundle the only 1.0.0 with Windows and Mac I think. For Linux we would need some logic, that identifies the right gstreamer available on the distribution. Maybe we could even reduce the effor

Re: Build r1829228 on Linux-32 (gstreamer build problem)

So that would mean that our 'official' community builds would not longer bundle/include it by default? Would we have 2 different versions of the extension (0.10 and 1.0) or just one? I like the idea, btw :) > On Apr 26, 2018, at 1:14 AM, Peter Kovacs wrote: > > Does it make sense to reorg the g

Re: Build r1829228 on Linux-32 (gstreamer build problem)

On 04/25/2018 10:14 PM, Peter Kovacs wrote: > Does it make sense to reorg the gstreamer module into an extention? > We could then have multiple versions of it. > > I mean after all this is only a optional feature, thats important to > some not all. I think this idea is very good and deserves seri

Re: Build r1829228 on Linux-32 (gstreamer build problem)

Does it make sense to reorg the gstreamer module into an extention? We could then have multiple versions of it. I mean after all this is only a optional feature, thats important to some not all. On 25.04.2018 16:18, Jim Jagielski wrote: I think this shows that we need to come to *some* consen

Re: Build r1829228 on Linux-32 (gstreamer build problem)

I think this shows that we need to come to *some* consensus on how to handle the gstreamer stuff. Either we provide both CentOS6 and Ubuntu builds to our community or we fold in the proposed gstreamer "work-around" which makes it a purely runtime concern. I would love to see how far we can go with

Re: Build r1829228 on Linux-32 (gstreamer build problem)

On Mon, Apr 23, 2018 at 1:50 AM, Peter Kovacs wrote: > Does the build work without gstreamer activated? > ​Yes, without gstreamer as part of the my config, I can build without issue. > > Am 23. April 2018 03:09:49 MESZ schrieb Kay Schenk : > >On Sun, Apr 22, 2018, 15:47 Andrea Pescetti > >w

Re: Build r1829228 on Linux-32 (gstreamer build problem)

Does the build work without gstreamer activated? Am 23. April 2018 03:09:49 MESZ schrieb Kay Schenk : >On Sun, Apr 22, 2018, 15:47 Andrea Pescetti >wrote: > >> Matthias Seidel wrote: >> > Am 23.04.2018 um 00:15 schrieb Andrea Pescetti: >> >> Correct. Jim's builds (not only releases) are done with

Re: Build Problem (solved)

On 08/08/2015 Jason Marshall wrote: build completed and I was able to install from the build. ... Hopefully from there I can tackle some of the smaller issues identified on Bugzilla and so make a meaningful contribution. Welcome Jason, congratulations and if you want to start making some small

Re: Build Problem (solved)

Hi Jason, Jason Marshall schrieb: Hi Regina Thank you for the advice here. I followed what you said and moved the source into the root of C drive, placing it in a directory with no special characters. I did subsequently encounter an issue with building the modules associated with the SDK, bu

Re: Build Problem (solved)

Hi Regina Thank you for the advice here. I followed what you said and moved the source into the root of C drive, placing it in a directory with no special characters. I did subsequently encounter an issue with building the modules associated with the SDK, but I re-ran configure with SDK disa

Re: Build Problem

Hi Jason, Jason Marshall schrieb: Hi Regina Thank you for looking at this. I have ensured that with a new Cygwin session I have run the following successfully: /source winenv.set.sh/ Following that, I have run the following: /build --all:comphelper 2>&1 | tee mybuild.log/ The bui

RE: Build Problem

03:11 +0200 > From: rb.hensc...@t-online.de > To: dev@openoffice.apache.org > Subject: Re: Build Problem > > Hi Jason, > > you have put the source into a folder under "tmp". I see the same in the > mail you referred. I'm not sure, but it might be, that this confuses &g

RE: Build Problem

y that is not temp? If so, would this simply be to the root of the Cygwin file system? If you require any further information, please do let me know. Thanks again. Jason > Date: Sat, 18 Jul 2015 20:03:11 +0200 > From: rb.hensc...@t-online.de > To: dev@openoffice.apache.org >

Re: Build Problem

Hi Jason, you have put the source into a folder under "tmp". I see the same in the mail you referred. I'm not sure, but it might be, that this confuses some path settings. Some curious errors appear, if the path settings are not applied or if build is called from a wrong directory. Please

Build Problem

Hi everyone I am attempting to build OpenOffice on Windows 7 32-bit having downloaded version 4.1.1 of the source code. I have got as far as calling build, but have encountered the following error which terminates the build: = Building module comphelper = Entering /tm

Re: Checked out revision 1547453 Build problem on Windows 7

Hello Vadim, I'm replying on the general mailing list again, because there are some points that may be of general interest. On 12.12.2013 08:43, Vadim Yedzinovich wrote: Successful build AOO 4.1.0! That's an important milestone. Congratulations! But I have to update C:\source\aoo-trunk\ma

Re: Checked out revision 1547453 Build problem on Windows 7

Hello Herbert, Have install Visual C++ 2008 Feature Pack Release. Go ahead but have another problem... Now with Handler.cxx: = Building module writerfilter = Entering /cygdrive/c/source/aoo-trunk/main/writerfilter/source/resourcemodel Entering /cygdrive/c/source/aoo-

Re: Checked out revision 1547453 Build problem on Windows 7

On 09.12.2013 17:46, Vadim Yedzinovich wrote: Hello Herbert, Commented: //namespace _STL //{ ///** @internal */ //template //inline ::rtl::Allocator & __stl_alloc_rebind (::rtl::Allocator & a, U const *) //{ //return (::rtl::Allocator&)(a); //} //} in C:\source\aoo-

Re: Checked out revision 1547453 Build problem on Windows 7

Hello Herbert, Commented: //namespace _STL //{ ///** @internal */ //template //inline ::rtl::Allocator & __stl_alloc_rebind (::rtl::Allocator & a, U const *) //{ //return (::rtl::Allocator&)(a); //} //} in C:\source\aoo-trunk\main\sal\inc\rtl\allocator.hxx *The next

Re: Checked out revision 1547453 Build problem on Windows 7

Hello Vadim, I'm replying on the mailing list, because this may be of interest to a wider audience. On 06.12.2013 18:58, Vadim Yedzinovich wrote: Get preprocess output to debugbase.i file (you can see it in attached file)... Got it, thanks! As I can see basic_string comes from namespace s

Re: Checked out revision 1547453 Build problem on Windows 7

Hello Vadim, On 06.12.2013 10:17, Vadim Yedzinovich wrote: MSVS or SDK was not updated. good. I've perform dmake clean: /cygdrive/c/source/aoo-trunk/main $ dmake clean rm -rf */wntmsci12.pro rm -rf solver/*/wntmsci12.pro rm -rf ../ext_librar

Re: Checked out revision 1547453 Build problem on Windows 7

Hi Vadim, On 04.12.2013 11:27, Vadim Yedzinovich wrote: $ svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk Receive AOO upgrade Checked out revision 1547453. The AOO revision you probably got was 1547747. Subversion reporting it as 1547453 is an artifact from the "all project

Checked out revision 1547453 Build problem on Windows 7

Hello, Windows 7, Cygwin64 Terminal With command: $ svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo-trunk Receive AOO upgrade Checked out revision 1547453. Try to rebuild it with command: $ build --all build -- version: 275224 Have error messages in sal module: = Bu

Re: build problem...missing oox/source/token/tokens.hxx

On Fri, Jul 5, 2013 at 10:11 AM, Kay Schenk wrote: > > > On Fri, Jul 5, 2013 at 9:02 AM, Herbert Duerr wrote: > >> On 05.07.2013 17:53, Kay Schenk wrote: >> >>> I'm trying to a build and seem to be missing oox/source/token/tokens.hxx >>> >>> referenced in oox/prj/d.lst >>> >>> I seem to have oo

Re: build problem...missing oox/source/token/tokens.hxx

On Fri, Jul 5, 2013 at 9:02 AM, Herbert Duerr wrote: > On 05.07.2013 17:53, Kay Schenk wrote: > >> I'm trying to a build and seem to be missing oox/source/token/tokens.hxx >> >> referenced in oox/prj/d.lst >> >> I seem to have oox/source/token/tokens.hxx.**head and >> oox/source/token/tokens.hxx

Re: build problem...missing oox/source/token/tokens.hxx

On 05.07.2013 17:53, Kay Schenk wrote: I'm trying to a build and seem to be missing oox/source/token/tokens.hxx referenced in oox/prj/d.lst I seem to have oox/source/token/tokens.hxx.head and oox/source/token/tokens.hxx.tail but no oox/source/token/tokens.hxx. Can d.lst be fixed to use these

build problem...missing oox/source/token/tokens.hxx

I'm trying to a build and seem to be missing oox/source/token/tokens.hxx referenced in oox/prj/d.lst I seem to have oox/source/token/tokens.hxx.head and oox/source/token/tokens.hxx.tail but no oox/source/token/tokens.hxx. Can d.lst be fixed to use these or has tokens.hxx been removed or ??? --

Re: Build problem on epm in the rejuvenate01 branche

Am 31.05.13 08:59, schrieb Herbert Dürr: Hi Raphael, On 2013/05/30 8:27 PM, Raphael Bircher wrote: Mac OS X 10.7 with XCode 4.3 My build stops at the epm modul. I know there is a workflow to find more details about the breaker, but I fergot it :-( Can sameone help me? Go into the module that

Re: Build problem on epm in the rejuvenate01 branche

Hi Raphael, On 2013/05/30 8:27 PM, Raphael Bircher wrote: Mac OS X 10.7 with XCode 4.3 My build stops at the epm modul. I know there is a workflow to find more details about the breaker, but I fergot it :-( Can sameone help me? Go into the module that had the problem and run build verbose=

Build problem on epm in the rejuvenate01 branche

Hi at all Mac OS X 10.7 with XCode 4.3 My build stops at the epm modul. I know there is a workflow to find more details about the breaker, but I fergot it :-( Can sameone help me? Thanks and greetings Raphael - To unsubscrib

Re: [BUILD PROBLEM] Fail on JPropex build.xml line 122 \\ Error 65280

Hi guys, I have some problems building ( see below). The guide I've used is the one at : http://wiki.openoffice.org/wiki/User:Dyrcona/LeopardBuild#flex The output I get after the following command : build --from l10ntools -P4 --dlv_switch -link is : BUILD FAILED /Users/maartenkesselaers/Docum

Re: [BUILD PROBLEM] Fail on JPropex build.xml line 122 \\ Error 65280

I'm building the total source in the terminal, not with Eclipse. The building guide that I used was the normal one for Mac OS X Snow Leopard. I haven't changed any classpath in my Java build env. Regards, Maarten Op 15-feb.-2013 09:32 schreef "Jürgen Schmidt" het volgende: > On 2/15/13 7:00 AM,

Re: [BUILD PROBLEM] Fail on JPropex build.xml line 122 \\ Error 65280

On 2/15/13 7:00 AM, Maarten Kesselaers wrote: > I have full working eclipse env and try to build on Mac OS X 10.6. > All prerequisits are installed as described in the guide. l10tools is normally build as all other modules in a command line environment triggered via makefiles. I am not aware that

Re: [BUILD PROBLEM] Fail on JPropex build.xml line 122 \\ Error 65280

I have full working eclipse env and try to build on Mac OS X 10.6. All prerequisits are installed as described in the guide. Thanks, Maarten Op 14-feb.-2013 09:33 schreef "Jürgen Schmidt" het volgende: > On 2/13/13 10:27 PM, Maarten Kesselaers wrote: > > My build just crashed on the build.xml un

Re: [BUILD PROBLEM] Fail on JPropex build.xml line 122 \\ Error 65280

On 2/13/13 10:27 PM, Maarten Kesselaers wrote: > My build just crashed on the build.xml under > ./main/l10ntools/java/jpropex/ at line 122 : > > 122classpathref="classpath"> > > So I guess I need to set a CLASSPATH, right? > To which directory should it be set? > do you have con

[BUILD PROBLEM] Fail on JPropex build.xml line 122 \\ Error 65280

My build just crashed on the build.xml under ./main/l10ntools/java/jpropex/ at line 122 : 122classpathref="classpath"> So I guess I need to set a CLASSPATH, right? To which directory should it be set? Thanks for your help, Regards, Maarten

Re: Re: Re: Re: build problem

Welcome! 2013/1/21 2 > Fan Zheng， > I'm so sorry for missing your reply because of my job. I have > finished the building with your help. > Thank you! > > Yi > At 2013-01-11 15:07:44,"Fan Zheng" wrote: > >Seems your cygwin did not to be allow to use system api to create process. > >Did

Re:Re: Re: Re: build problem

Fan Zheng， I'm so sorry for missing your reply because of my job. I have finished the building with your help. Thank you! Yi At 2013-01-11 15:07:44,"Fan Zheng" wrote: >Seems your cygwin did not to be allow to use system api to create process. >Did you use some kind of anti-virus applic

Re: Re: Re: build problem

Seems your cygwin did not to be allow to use system api to create process. Did you use some kind of anti-virus application like Symantec EndPoint Protection? If yes, you may need to install a newly version with certain verification for cygwin. BTW, the method you executed last one "make -sr" will

Re:Re: Re: build problem

After my step 2, I go to sw and run "build debug=true", but it didn'i work. I got the message: >/cygdrive/d/aoo/main/sw >$ build debug=true cygwin warning: MS-DOS style path detected: D:/aoo/main/solenv/bin/build.pl Preferred POSIX equivalent is: /cygdrive/d/aoo/main/solenv/bin/build.pl CYG

Re: Re: build problem

I am not sure your step 4,5,6...After your step 2, you can go to sw module and run "build debug=true" to do individual build with debug info once you have done modifications in sw module,and then you will find that breakpoints can be added to your modified files after the new built dlls at ..\main\

Re:Re: build problem

Hi, I have found the dlls in solver folder, but I was another problem, when build sw with debug information, but I couldn't found the dlls with debug infomation, where are them? there are the command I input in cygwin: 1.cd main 2.source winenv.Set.sh 4.cd instsetoo_native

Re:Re: build problem

Hi Jianhong Cheng, Thank you, I got it. Yi At 2013-01-09 16:32:46,chengjh wrote: >Sure,the compiled object files can be found at ..\main\solver\350\ >wntmsci12.pro\workdir\CxxObject\sw\.,and dlls can be got >from ..\main\solver\350\wntmsci12.pro\workdir\LinkTarget\Library..Thanks. > >On W

Re:Re: build problem

Herbert, Thank you! I gain a lot from you At 2013-01-09 15:52:47,"Herbert Duerr" wrote: >On 09.01.2013 08:06, 2 wrote: >> when got my own build, I couldn't found the filefolder wntmsci12.pro in >> sw module which be found in sc module, could it be said that my build failed >> ? > >Th

Re: build problem

Sure,the compiled object files can be found at ..\main\solver\350\ wntmsci12.pro\workdir\CxxObject\sw\.,and dlls can be got from ..\main\solver\350\wntmsci12.pro\workdir\LinkTarget\Library..Thanks. On Wed, Jan 9, 2013 at 3:52 PM, Herbert Duerr wrote: > On 09.01.2013 08:06, 2 wrote: > >> whe

Re: build problem

On 09.01.2013 08:06, 2 wrote: when got my own build, I couldn't found the filefolder wntmsci12.pro in sw module which be found in sc module, could it be said that my build failed ? That is no problem: The sw module has been converted to gbuild, so that the files are now in main/solver/35

build problem

Hi, when got my own build, I couldn't found the filefolder wntmsci12.pro in sw module which be found in sc module, could it be said that my build failed ? Yi