Re: [dev] Was : problem building comphelper on MIPS

Hi Eric and all, On Thu, Feb 4, 2010 at 2:48 PM, eric b eric.bach...@free.fr wrote: Hi, Sorry, I missed the original message, but I'll try to answer to the original message, who is : http://www.openoffice.org/servlets/ReadMsg ?listName=devmsgNo=26295 First, I got the same issue, and I'm

Re: [dev] Was : problem building comphelper on MIPS

Le 5 févr. 10 à 09:03, Zhang Xiaofei a écrit : Hi Eric and all, Hi Felix, For people who don't know, I'm colleague of the author of the original message, we build on Fuloong Minis, which has same processors as Gdium machines has. Ok. I observed the build output and found the

Re: [dev] Was : problem building comphelper on MIPS

Hi Eric and all, On Thu, Feb 4, 2010 at 2:48 PM, eric b eric.bach...@free.fr wrote: Hi, Sorry, I missed the original message, but I'll try to answer to the original message, who is : http://www.openoffice.org/servlets/ReadMsg ?listName=devmsgNo=26295 First, I got the same issue, and I'm

Re: [dev] Was : problem building comphelper on MIPS

Hi Eric and all, On Thu, Feb 4, 2010 at 2:48 PM, eric b eric.bach...@free.fr wrote: Hi, Sorry, I missed the original message, but I'll try to answer to the original message, who is : http://www.openoffice.org/servlets/ReadMsg ?listName=devmsgNo=26295 First, I got the same issue, and I'm

RE: [dev] Re: dmake error: while building ucbhelper

Thanks! i will give this a try. -Original Message- From: Caolán McNamara caol...@redhat.com Sent: Tuesday, February 02, 2010 12:50 AM To: dev@openoffice.org dev@openoffice.org Subject: Re: [dev] Re: dmake error: while building ucbhelper On Mon, 2010-02-01 at 11:50 +0100, Michael

Re: [dev] Was : problem building comphelper on MIPS

On Thu, 2010-02-04 at 07:48 +0100, eric b wrote: The first thing I found was a missing -fpic flag in the solenv/inc/ unxlngmips.mk -fpic is not missing from unxlngmips.mk. unxlngmips.mk inherits from unxlng.mk and unxlng.mk defaults to -fpic for PICSWITCH so unless it needs to use e.g. -fPIC

Re: [dev] Was : problem building comphelper on MIPS

On Fri, 2010-02-05 at 09:19 +0100, eric b wrote: Till now we have tested DEV300_m58 and DEV300_m60, the breakage took place in the latter but not the former one. And it was *definitely* the same compiler and tool chain used in both cases right ? And the error in question is ...

Re: [dev] Was : problem building comphelper on MIPS

Hi Caolan, Le 5 févr. 10 à 10:05, Caolán McNamara a écrit : On Thu, 2010-02-04 at 07:48 +0100, eric b wrote: The first thing I found was a missing -fpic flag in the solenv/inc/ unxlngmips.mk -fpic is not missing from unxlngmips.mk. unxlngmips.mk inherits from unxlng.mk and unxlng.mk

Re: [dev] Was : problem building comphelper on MIPS

Hi, Le 5 févr. 10 à 10:15, Caolán McNamara a écrit : On Fri, 2010-02-05 at 09:19 +0100, eric b wrote: Till now we have tested DEV300_m58 and DEV300_m60, the breakage took place in the latter but not the former one. And it was *definitely* the same compiler and tool chain used in both

Re: [dev] Was : problem building comphelper on MIPS

On Fri, 2010-02-05 at 10:30 +0100, eric b wrote: Hi, Le 5 févr. 10 à 10:15, Caolán McNamara a écrit : On Fri, 2010-02-05 at 09:19 +0100, eric b wrote: Till now we have tested DEV300_m58 and DEV300_m60, the breakage took place in the latter but not the former one. And it was

[dev] building OOo 3.1.1 and OOo 3.1.0 in debugging mode and how to start the built application

Hello, I was trying to build OOo 3.1.1 and OOo 3.1.0 in debugging mode. I had the same issue as the below one. http://qa.openoffice.org/issues/show_bug.cgi?id=82773 But according to the above report, the reporter could still start open office, but I am not able to launch it. Nothing was built

[dev] svx module split a little bit more: new editeng module

Hi, starting with the DEV300m72 build there is a new module called editeng that was split off from svx. This module has no dependencies on svx and also no dependencies on sfx2. OTOH, svx depends on editeng (as the editengine and outliner objects are used in shapes). The moved code comprises the

Re: [dev] svx module split a little bit more: new editeng module

Hi Mathias, starting with the DEV300m72 build there is a new module called editeng that was split off from svx. ... This is the second step in the continuing effort to reduce the size of the svx module. Though a few unnecessary files could be removed, this will not reduce the code size of

[dev] DEV300_m72: Module goodies removed

Hi, the module goodies contained a lot of unused header files, a single base3dtrans.cxx, the GraphicObject code and some graphic filters. These filters are loaded on demand and don't create any link dependencies. I moved all the filters into the module filter, the b3dtrans.cxx into tools and the

Re: [dev] DEV300_m72: Module goodies removed

I moved all the filters into the module filter, the b3dtrans.cxx into tools and the GraphicObject code into svtools. The module goodies then could be removed. This change will be effective starting with DEV300_m72. StarInvaders gone? -- Pavel Janík

Re: [dev] DEV300_m72: Module goodies removed

Pavel Janík wrote: I moved all the filters into the module filter, the b3dtrans.cxx into tools and the GraphicObject code into svtools. The module goodies then could be removed. This change will be effective starting with DEV300_m72. StarInvaders gone? Yes. But talking about

[dev] the links in http://qa.openoffice.org/issues/show_bug.cgi?id=82773 are broken

Hello, I am having the same issue as http://qa.openoffice.org/issues/show_bug.cgi?id=82773, I am using the second method metioned below to make the osl less noisy. But I am curious what is the third solution really about, I was looking at TestComponent.cxx, but couldn't figure out what mean by