Re: 4.2.0: Build for ARM

2017-11-28 Thread Damjan Jovanovic 
Not sure about the Arduino, but the Raspberry Pi is usable as a desktop
computer, with a keyboard/mouse/screen.


On Wed, Nov 29, 2017 at 12:26 AM, Peter kovacs  wrote:

> How can anduino and rasperry machines referred to?
>
> Am 28. November 2017 10:55:21 MEZ schrieb Damjan Jovanovic <
> dam...@apache.org>:
> >What do you mean by category?
> >
> >On Tue, Nov 28, 2017 at 11:21 AM, Peter kovacs 
> >wrote:
> >
> >> What's the category for those?
> >>
> >> Am 28. November 2017 08:42:17 MEZ schrieb Damjan Jovanovic <
> >> dam...@apache.org>:
> >> >Raspberry Pis?
> >> >
> >> >On Tue, Nov 28, 2017 at 9:41 AM, Peter kovacs 
> >wrote:
> >> >
> >> >> Maybe the patch is interesting to AndroOffice? Anyone from them on
> >> >our
> >> >> list?
> >> >>
> >> >> In general I'd say that we need a different gui for touch screen
> >> >devices.
> >> >>
> >> >> The other case is I can think of ARM processors is arduino
> >machines
> >> >with
> >> >> Linux installed. Don't know if this is a use case at all.
> >> >>
> >> >> Am 27. November 2017 23:46:27 MEZ schrieb Marcus
> >> >:
> >> >> >Am 24.11.2017 um 23:16 schrieb FR web forum:
> >> >> >> Here: https://bz.apache.org/ooo/show_bug.cgi?id=127040
> >> >> >> Eric Bachard provide a patch to build AOO on Linux ARM (32
> >bits).
> >> >> >>
> >> >> >> Maybe a good point for next 4.2.0?
> >> >> >
> >> >> >I don't know how relevant the ARM architecture still is and if an
> >> >> >office
> >> >> >suite is useful for it. However, someone needs to take care of
> >the
> >> >> >ability for building on this platform. A patch is nice but is not
> >> >> >enough
> >> >> >for future changes within the whole code base.
> >> >> >
> >> >> >My 2 ct
> >> >> >
> >> >> >Marcus
> >> >> >
> >> >> >
> >> >>
> >>
> >>>-
> >> >> >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> >> >For additional commands, e-mail: dev-h...@openoffice.apache.org
> >> >>
> >> >>
> >-
> >> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >> >>
> >> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: a more sane way to override optimization flags in gbuild

2017-11-28 Thread Don Lewis 
On 28 Nov, Jim Jagielski wrote:
> Wouldn't it make sense to do something like LOCAL_CFLAGS which
> could then be manipulated?...

It depends on what the goal is.  What would be nice is if debug flags
and optimization flags could be specified from the environment in CFLAGS
to override the defaults, but the per-target optimization level would
override that if it was lower.  Sounds difficult, though ...


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

Re: Fwd: [apache/openoffice] Fix typo (#4)

2017-11-28 Thread Peter kovacs 
I think they are only read-only.
I do not have any way in manipulating requests on GitHub.
So the only way is to do what you did.

Am 28. November 2017 23:44:28 MEZ schrieb Matthias Seidel 
:
>Anyway, this is a pull request for AOO415!
>Should we make the branches "read-only" on Github?
>
>I will correct the typo in trunk. And a second one I found in the same
>comment... ;-)
>
>Regards, Matthias
>
>
>Am 28.11.2017 um 20:53 schrieb Matthias Seidel:
>>
>> We have a new pull request on Github...
>>
>> Just out of interest: If we would review and approve this (small)
>> patch, would it become visible in subversion?
>>
>> Regards, Matthias
>>
>>
>>
>>  Weitergeleitete Nachricht 
>> Betreff: [apache/openoffice] Fix typo (#4)
>> Datum:   Tue, 28 Nov 2017 12:33:57 + (UTC)
>> Von: Luan Kevin Ferreira 
>> Antwort an:  apache/openoffice
>>
>
>>
>> An:  apache/openoffice 
>> Kopie (CC):  Subscribed 
>>
>>
>>
>>
>
>>
>>
>> You can view, comment on, or merge this pull request online
>at:
>>
>>   https://github.com/apache/openoffice/pull/4
>>
>>
>> Commit Summary
>>
>>   * Fix typo
>>
>>
>> File Changes
>>
>>   * *M* main/extensions/source/config/ldap/ldapuserprofilebe.hxx
>>  (2)
>>
>>
>> Patch Links:
>>
>>   * https://github.com/apache/openoffice/pull/4.patch
>>   * https://github.com/apache/openoffice/pull/4.diff
>>
>> —
>> You are receiving this because you are subscribed to this thread.
>> Reply to this email directly, view it on GitHub
>> , or mute the thread
>>
>.
>>

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

Re: 4.2.0: Build for ARM

2017-11-28 Thread Peter kovacs 
How can anduino and rasperry machines referred to?

Am 28. November 2017 10:55:21 MEZ schrieb Damjan Jovanovic :
>What do you mean by category?
>
>On Tue, Nov 28, 2017 at 11:21 AM, Peter kovacs 
>wrote:
>
>> What's the category for those?
>>
>> Am 28. November 2017 08:42:17 MEZ schrieb Damjan Jovanovic <
>> dam...@apache.org>:
>> >Raspberry Pis?
>> >
>> >On Tue, Nov 28, 2017 at 9:41 AM, Peter kovacs 
>wrote:
>> >
>> >> Maybe the patch is interesting to AndroOffice? Anyone from them on
>> >our
>> >> list?
>> >>
>> >> In general I'd say that we need a different gui for touch screen
>> >devices.
>> >>
>> >> The other case is I can think of ARM processors is arduino
>machines
>> >with
>> >> Linux installed. Don't know if this is a use case at all.
>> >>
>> >> Am 27. November 2017 23:46:27 MEZ schrieb Marcus
>> >:
>> >> >Am 24.11.2017 um 23:16 schrieb FR web forum:
>> >> >> Here: https://bz.apache.org/ooo/show_bug.cgi?id=127040
>> >> >> Eric Bachard provide a patch to build AOO on Linux ARM (32
>bits).
>> >> >>
>> >> >> Maybe a good point for next 4.2.0?
>> >> >
>> >> >I don't know how relevant the ARM architecture still is and if an
>> >> >office
>> >> >suite is useful for it. However, someone needs to take care of
>the
>> >> >ability for building on this platform. A patch is nice but is not
>> >> >enough
>> >> >for future changes within the whole code base.
>> >> >
>> >> >My 2 ct
>> >> >
>> >> >Marcus
>> >> >
>> >> >
>> >>
>>
>>>-
>> >> >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> >> >For additional commands, e-mail: dev-h...@openoffice.apache.org
>> >>
>> >>
>-
>> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> >>
>> >>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>

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

Re: Fwd: [apache/openoffice] Fix typo (#4)

2017-11-28 Thread Matthias Seidel 
Anyway, this is a pull request for AOO415!
Should we make the branches "read-only" on Github?

I will correct the typo in trunk. And a second one I found in the same
comment... ;-)

Regards, Matthias


Am 28.11.2017 um 20:53 schrieb Matthias Seidel:
>
> We have a new pull request on Github...
>
> Just out of interest: If we would review and approve this (small)
> patch, would it become visible in subversion?
>
> Regards, Matthias
>
>
>
>  Weitergeleitete Nachricht 
> Betreff:  [apache/openoffice] Fix typo (#4)
> Datum:Tue, 28 Nov 2017 12:33:57 + (UTC)
> Von:  Luan Kevin Ferreira 
> Antwort an:   apache/openoffice
> 
>
> An:   apache/openoffice 
> Kopie (CC):   Subscribed 
>
>
>
> 
>
>
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/apache/openoffice/pull/4
>
>
> Commit Summary
>
>   * Fix typo
>
>
> File Changes
>
>   * *M* main/extensions/source/config/ldap/ldapuserprofilebe.hxx
>  (2)
>
>
> Patch Links:
>
>   * https://github.com/apache/openoffice/pull/4.patch
>   * https://github.com/apache/openoffice/pull/4.diff
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> , or mute the thread
> .
>



smime.p7s
Description: S/MIME Cryptographic Signature

Fwd: [Solved] Graphs are blank after upgrading to 4.1.4 (Mac OS)

2017-11-28 Thread Hoogeveen, Rick 
Hello,
Rory recommended I send this feedback to this address.  Please see below.  
Context:  I am the author of the post with the title listed in this message’s 
Subject line.  I’ve been trying out the fix that hasn’t been made available due 
to the issues it caused in Base.  I haven’t had any issues with it until today, 
so I’m not sure if this was just a corruption/glitch to one sheet, or if it’s 
related.

Thank you,

Rick Hoogeveen
Continuous Improvement
The Mitographers, Inc.
605-731-0141






Begin forwarded message:

From: Rick Hoogeveen mailto:hoo...@mito.com>>
Subject: Fwd: [Solved] Graphs are blank after upgrading to 4.1.4 (Mac OS)
Date: November 28, 2017 at 11:39:59 AM CST
To: Rory O'Farrell mailto:ofarr...@iol.ie>>

I meant to include that I am also unable to create a new text box in this 
sheet.  I ended up copying the first sheet, then creating a new text box.
--Rick


Begin forwarded message:

From: Rick Hoogeveen mailto:hoo...@mito.com>>
Subject: Re: [Solved] Graphs are blank after upgrading to 4.1.4 (Mac OS)
Date: November 28, 2017 at 11:28:36 AM CST
To: Rory O'Farrell mailto:ofarr...@iol.ie>>

Hi Rory,
Not sure if this is a bug related to the fix listed below or not:  I’m working 
in Calc and making a feature matrix--comparing features that digital printers 
offer.  In my “Speeds” column, I had created a text box to list the various 
print speeds.  I then copied that text box over a week ago when populating the 
other rows with data.  I’m adding other columns and rows today and wanted to 
copy the text box again.  Today, no matter how I try copying the text box, it 
copies it, but pastes it in the top rows of the sheet, and I can’t drag it or 
move it down to the appropriate row.  I tried adjusting how the text box was 
anchored, and also unfroze the column I had frozen.

Screen shots are attached (scroll to the end of the message to see them (Mac to 
PC email thing)).

Have you come across this issue before?

Thanks,
Rick



On Nov 2, 2017, at 5:55 AM, Rory O'Farrell 
mailto:ofarr...@iol.ie>> wrote:

The URL for download is
https://dist.apache.org/repos/dist/dev/openoffice/macOS-4.1.4-20171101

Please keep this confidential at present; if you find any problems, please let 
me know with details so I can pass them on to the DEV list.

--
Rory O'Farrell mailto:ofarr...@iol.ie>>
[cid:7FFE4CBC-6ACD-4C54-A5DE-C82E61DBA2C8@Mito.Local][cid:51D84898-98FD-4292-A207-7093147BFFB3@Mito.Local][cid:52BB08BF-CD91-4EC4-B6B3-3D7A5064809C@Mito.Local]

Fwd: [apache/openoffice] Fix typo (#4)

2017-11-28 Thread Matthias Seidel 
We have a new pull request on Github...

Just out of interest: If we would review and approve this (small) patch,
would it become visible in subversion?

Regards, Matthias



 Weitergeleitete Nachricht 
Betreff:[apache/openoffice] Fix typo (#4)
Datum:  Tue, 28 Nov 2017 12:33:57 + (UTC)
Von:Luan Kevin Ferreira 
Antwort an: apache/openoffice


An: apache/openoffice 
Kopie (CC): Subscribed 






You can view, comment on, or merge this pull request online at:

  https://github.com/apache/openoffice/pull/4


Commit Summary

  * Fix typo


File Changes

  * *M* main/extensions/source/config/ldap/ldapuserprofilebe.hxx
 (2)


Patch Links:

  * https://github.com/apache/openoffice/pull/4.patch
  * https://github.com/apache/openoffice/pull/4.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
, or mute the thread
.



smime.p7s
Description: S/MIME Cryptographic Signature

Re: a more sane way to override optimization flags in gbuild

2017-11-28 Thread Jim Jagielski 
Wouldn't it make sense to do something like LOCAL_CFLAGS which
could then be manipulated?...

What I might do is commit this and then work on that ;)

> On Nov 28, 2017, at 4:42 AM, Don Lewis  wrote:
> 
> Here's a gbuild patch vs. trunk r1816518 that makes setting optimization
> level overrides for specific files a lot easier.  I also added a way to
> safely specify -O1 without breaking debug.  It's not perfect because if
> someone set CXXFLAGS in the environment, it will override the override
> in the .mk file.  It is only very lightly tested ... my FreeBSD build is
> only about halfway complete.
> 
> Index: main/framework/Library_fwk.mk
> ===
> --- main/framework/Library_fwk.mk (revision 1816518)
> +++ main/framework/Library_fwk.mk (working copy)
> @@ -61,6 +61,11 @@
>   $(gb_STDLIBS) \
> ))
> 
> +# i126622 - Base 4.1.2 does not open Tables and Queries in Mac OSX
> +ifeq ($(OS),MACOSX)
> +$(call 
> gb_LinkTarget_set_cxx_optimization,framework/source/loadenv/loadenv,$(gb_COMPILEROPT1FLAGS))
> +endif
> +
> $(eval $(call gb_Library_add_exception_objects,fwk,\
>   framework/source/accelerators/acceleratorcache \
>   framework/source/accelerators/acceleratorconfiguration \
> @@ -190,10 +195,4 @@
>   framework/source/xml/imagesdocumenthandler \
> ))
> 
> -# i126622 - Base 4.1.2 does not open Tables and Queries in Mac OSX
> -ifeq ($(OS),MACOSX)
> -$(call gb_CxxObject_get_target,framework/source/loadenv/loadenv):\
> - T_CXXFLAGS := $(gb_LinkTarget_CXXFLAGS) $(gb_LinkTarget_EXCEPTIONFLAGS) 
> $(gb_COMPILERNOOPTFLAGS)
> -endif
> -
> # vim: set noet sw=4 ts=4:
> Index: main/solenv/gbuild/LinkTarget.mk
> ===
> --- main/solenv/gbuild/LinkTarget.mk  (revision 1816518)
> +++ main/solenv/gbuild/LinkTarget.mk  (working copy)
> @@ -333,12 +333,12 @@
> $(call gb_LinkTarget_get_clean_target,$(1)) \
> $(call gb_LinkTarget_get_target,$(1)) : GENCXXOBJECTS :=
> $(call gb_LinkTarget_get_headers_target,$(1)) \
> -$(call gb_LinkTarget_get_target,$(1)) : T_CFLAGS := $$(gb_LinkTarget_CFLAGS) 
> $(CFLAGS)
> +$(call gb_LinkTarget_get_target,$(1)) : T_CFLAGS := $$(gb_LinkTarget_CFLAGS)
> $(call gb_LinkTarget_get_headers_target,$(1)) \
> $(call gb_LinkTarget_get_target,$(1)) : T_CXXFLAGS := 
> $$(gb_LinkTarget_CXXFLAGS)
> $(call gb_LinkTarget_get_headers_target,$(1)) \
> -$(call gb_LinkTarget_get_target,$(1)) : PCH_CXXFLAGS := 
> $$(gb_LinkTarget_CXXFLAGS) $(CXXFLAGS)
> -$(call gb_LinkTarget_get_target,$(1)) : T_OBJCXXFLAGS := 
> $$(gb_LinkTarget_OBJCXXFLAGS) $(OBJCXXFLAGS)
> +$(call gb_LinkTarget_get_target,$(1)) : PCH_CXXFLAGS := 
> $$(gb_LinkTarget_CXXFLAGS)
> +$(call gb_LinkTarget_get_target,$(1)) : T_OBJCXXFLAGS := 
> $$(gb_LinkTarget_OBJCXXFLAGS)
> $(call gb_LinkTarget_get_headers_target,$(1)) \
> $(call gb_LinkTarget_get_target,$(1)) : DEFS := $$(gb_LinkTarget_DEFAULTDEFS) 
> $(CPPFLAGS)
> $(call gb_LinkTarget_get_headers_target,$(1)) \
> @@ -367,10 +367,10 @@
> $(call gb_LinkTarget_get_dep_target,$(1)) : CXXOBJECTS := 
> $(call gb_LinkTarget_get_dep_target,$(1)) : OBJCXXOBJECTS :=
> $(call gb_LinkTarget_get_dep_target,$(1)) : GENCXXOBJECTS :=
> -$(call gb_LinkTarget_get_dep_target,$(1)) : T_CFLAGS := 
> $$(gb_LinkTarget_CFLAGS) $(CFLAGS)
> +$(call gb_LinkTarget_get_dep_target,$(1)) : T_CFLAGS := 
> $$(gb_LinkTarget_CFLAGS)
> $(call gb_LinkTarget_get_dep_target,$(1)) : T_CXXFLAGS := 
> $$(gb_LinkTarget_CXXFLAGS)
> -$(call gb_LinkTarget_get_dep_target,$(1)) : PCH_CXXFLAGS := 
> $$(gb_LinkTarget_CXXFLAGS) $(CXXFLAGS)
> -$(call gb_LinkTarget_get_dep_target,$(1)) : T_OBJCXXFLAGS := 
> $$(gb_LinkTarget_OBJCXXFLAGS) $(OBJCXXFLAGS)
> +$(call gb_LinkTarget_get_dep_target,$(1)) : PCH_CXXFLAGS := 
> $$(gb_LinkTarget_CXXFLAGS)
> +$(call gb_LinkTarget_get_dep_target,$(1)) : T_OBJCXXFLAGS := 
> $$(gb_LinkTarget_OBJCXXFLAGS)
> $(call gb_LinkTarget_get_dep_target,$(1)) : DEFS := 
> $$(gb_LinkTarget_DEFAULTDEFS) $(CPPFLAGS)
> $(call gb_LinkTarget_get_dep_target,$(1)) : PCH_DEFS := 
> $$(gb_LinkTarget_DEFAULTDEFS) $(CPPFLAGS)
> $(call gb_LinkTarget_get_dep_target,$(1)) : INCLUDE := 
> $$(gb_LinkTarget_INCLUDE)
> @@ -477,9 +477,24 @@
> $(call gb_LinkTarget_get_dep_target,$(1)) : T_OBJCXXFLAGS := $(2)
> endif
> endif
> +endef
> 
> +define gb_LinkTarget_set_c_optimization
> +$(call gb_CObject_get_target,$(1)) : gb_COMPILEROPTFLAGS := $(2)
> endef
> 
> +define gb_LinkTarget_set_cxx_optimization
> +$(call gb_CxxObject_get_target,$(1)) : gb_COMPILEROPTFLAGS := $(2)
> +endef
> +
> +define gb_LinkTarget_set_gencxx_optimization
> +$(call gb_GenCxxObject_get_target,$(1)) : gb_COMPILEROPTFLAGS := $(2)
> +endef
> +
> +define gb_LinkTarget_set_objcxx_optimization
> +$(call gb_ObjCxxObject_get_target,$(1)) : gb_COMPILEROPTFLAGS := $(2)
> +endef
> +
> define gb_LinkTarget_set_include
> $(call gb_LinkTarget_get_headers_target,$(1)) \
> $(call gb_LinkTarget_get_target,$(1)) : INCLUDE := $(2)
> @@ -635

Re: 4.2.0: Build for ARM

2017-11-28 Thread Damjan Jovanovic 
What do you mean by category?

On Tue, Nov 28, 2017 at 11:21 AM, Peter kovacs  wrote:

> What's the category for those?
>
> Am 28. November 2017 08:42:17 MEZ schrieb Damjan Jovanovic <
> dam...@apache.org>:
> >Raspberry Pis?
> >
> >On Tue, Nov 28, 2017 at 9:41 AM, Peter kovacs  wrote:
> >
> >> Maybe the patch is interesting to AndroOffice? Anyone from them on
> >our
> >> list?
> >>
> >> In general I'd say that we need a different gui for touch screen
> >devices.
> >>
> >> The other case is I can think of ARM processors is arduino machines
> >with
> >> Linux installed. Don't know if this is a use case at all.
> >>
> >> Am 27. November 2017 23:46:27 MEZ schrieb Marcus
> >:
> >> >Am 24.11.2017 um 23:16 schrieb FR web forum:
> >> >> Here: https://bz.apache.org/ooo/show_bug.cgi?id=127040
> >> >> Eric Bachard provide a patch to build AOO on Linux ARM (32 bits).
> >> >>
> >> >> Maybe a good point for next 4.2.0?
> >> >
> >> >I don't know how relevant the ARM architecture still is and if an
> >> >office
> >> >suite is useful for it. However, someone needs to take care of the
> >> >ability for building on this platform. A patch is nice but is not
> >> >enough
> >> >for future changes within the whole code base.
> >> >
> >> >My 2 ct
> >> >
> >> >Marcus
> >> >
> >> >
> >>
> >>-
> >> >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> >For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

a more sane way to override optimization flags in gbuild

2017-11-28 Thread Don Lewis 
Here's a gbuild patch vs. trunk r1816518 that makes setting optimization
level overrides for specific files a lot easier.  I also added a way to
safely specify -O1 without breaking debug.  It's not perfect because if
someone set CXXFLAGS in the environment, it will override the override
in the .mk file.  It is only very lightly tested ... my FreeBSD build is
only about halfway complete.

Index: main/framework/Library_fwk.mk
===
--- main/framework/Library_fwk.mk   (revision 1816518)
+++ main/framework/Library_fwk.mk   (working copy)
@@ -61,6 +61,11 @@
$(gb_STDLIBS) \
 ))
 
+# i126622 - Base 4.1.2 does not open Tables and Queries in Mac OSX
+ifeq ($(OS),MACOSX)
+$(call 
gb_LinkTarget_set_cxx_optimization,framework/source/loadenv/loadenv,$(gb_COMPILEROPT1FLAGS))
+endif
+
 $(eval $(call gb_Library_add_exception_objects,fwk,\
framework/source/accelerators/acceleratorcache \
framework/source/accelerators/acceleratorconfiguration \
@@ -190,10 +195,4 @@
framework/source/xml/imagesdocumenthandler \
 ))
 
-# i126622 - Base 4.1.2 does not open Tables and Queries in Mac OSX
-ifeq ($(OS),MACOSX)
-$(call gb_CxxObject_get_target,framework/source/loadenv/loadenv):\
-   T_CXXFLAGS := $(gb_LinkTarget_CXXFLAGS) $(gb_LinkTarget_EXCEPTIONFLAGS) 
$(gb_COMPILERNOOPTFLAGS)
-endif
-
 # vim: set noet sw=4 ts=4:
Index: main/solenv/gbuild/LinkTarget.mk
===
--- main/solenv/gbuild/LinkTarget.mk(revision 1816518)
+++ main/solenv/gbuild/LinkTarget.mk(working copy)
@@ -333,12 +333,12 @@
 $(call gb_LinkTarget_get_clean_target,$(1)) \
 $(call gb_LinkTarget_get_target,$(1)) : GENCXXOBJECTS :=
 $(call gb_LinkTarget_get_headers_target,$(1)) \
-$(call gb_LinkTarget_get_target,$(1)) : T_CFLAGS := $$(gb_LinkTarget_CFLAGS) 
$(CFLAGS)
+$(call gb_LinkTarget_get_target,$(1)) : T_CFLAGS := $$(gb_LinkTarget_CFLAGS)
 $(call gb_LinkTarget_get_headers_target,$(1)) \
 $(call gb_LinkTarget_get_target,$(1)) : T_CXXFLAGS := 
$$(gb_LinkTarget_CXXFLAGS)
 $(call gb_LinkTarget_get_headers_target,$(1)) \
-$(call gb_LinkTarget_get_target,$(1)) : PCH_CXXFLAGS := 
$$(gb_LinkTarget_CXXFLAGS) $(CXXFLAGS)
-$(call gb_LinkTarget_get_target,$(1)) : T_OBJCXXFLAGS := 
$$(gb_LinkTarget_OBJCXXFLAGS) $(OBJCXXFLAGS)
+$(call gb_LinkTarget_get_target,$(1)) : PCH_CXXFLAGS := 
$$(gb_LinkTarget_CXXFLAGS)
+$(call gb_LinkTarget_get_target,$(1)) : T_OBJCXXFLAGS := 
$$(gb_LinkTarget_OBJCXXFLAGS)
 $(call gb_LinkTarget_get_headers_target,$(1)) \
 $(call gb_LinkTarget_get_target,$(1)) : DEFS := $$(gb_LinkTarget_DEFAULTDEFS) 
$(CPPFLAGS)
 $(call gb_LinkTarget_get_headers_target,$(1)) \
@@ -367,10 +367,10 @@
 $(call gb_LinkTarget_get_dep_target,$(1)) : CXXOBJECTS := 
 $(call gb_LinkTarget_get_dep_target,$(1)) : OBJCXXOBJECTS :=
 $(call gb_LinkTarget_get_dep_target,$(1)) : GENCXXOBJECTS :=
-$(call gb_LinkTarget_get_dep_target,$(1)) : T_CFLAGS := 
$$(gb_LinkTarget_CFLAGS) $(CFLAGS)
+$(call gb_LinkTarget_get_dep_target,$(1)) : T_CFLAGS := 
$$(gb_LinkTarget_CFLAGS)
 $(call gb_LinkTarget_get_dep_target,$(1)) : T_CXXFLAGS := 
$$(gb_LinkTarget_CXXFLAGS)
-$(call gb_LinkTarget_get_dep_target,$(1)) : PCH_CXXFLAGS := 
$$(gb_LinkTarget_CXXFLAGS) $(CXXFLAGS)
-$(call gb_LinkTarget_get_dep_target,$(1)) : T_OBJCXXFLAGS := 
$$(gb_LinkTarget_OBJCXXFLAGS) $(OBJCXXFLAGS)
+$(call gb_LinkTarget_get_dep_target,$(1)) : PCH_CXXFLAGS := 
$$(gb_LinkTarget_CXXFLAGS)
+$(call gb_LinkTarget_get_dep_target,$(1)) : T_OBJCXXFLAGS := 
$$(gb_LinkTarget_OBJCXXFLAGS)
 $(call gb_LinkTarget_get_dep_target,$(1)) : DEFS := 
$$(gb_LinkTarget_DEFAULTDEFS) $(CPPFLAGS)
 $(call gb_LinkTarget_get_dep_target,$(1)) : PCH_DEFS := 
$$(gb_LinkTarget_DEFAULTDEFS) $(CPPFLAGS)
 $(call gb_LinkTarget_get_dep_target,$(1)) : INCLUDE := 
$$(gb_LinkTarget_INCLUDE)
@@ -477,9 +477,24 @@
 $(call gb_LinkTarget_get_dep_target,$(1)) : T_OBJCXXFLAGS := $(2)
 endif
 endif
+endef
 
+define gb_LinkTarget_set_c_optimization
+$(call gb_CObject_get_target,$(1)) : gb_COMPILEROPTFLAGS := $(2)
 endef
 
+define gb_LinkTarget_set_cxx_optimization
+$(call gb_CxxObject_get_target,$(1)) : gb_COMPILEROPTFLAGS := $(2)
+endef
+
+define gb_LinkTarget_set_gencxx_optimization
+$(call gb_GenCxxObject_get_target,$(1)) : gb_COMPILEROPTFLAGS := $(2)
+endef
+
+define gb_LinkTarget_set_objcxx_optimization
+$(call gb_ObjCxxObject_get_target,$(1)) : gb_COMPILEROPTFLAGS := $(2)
+endef
+
 define gb_LinkTarget_set_include
 $(call gb_LinkTarget_get_headers_target,$(1)) \
 $(call gb_LinkTarget_get_target,$(1)) : INCLUDE := $(2)
@@ -635,7 +650,7 @@
 
 $(call gb_LinkTarget_get_target,$(1)) : $(call gb_GenCxxObject_get_target,$(2))
 $(call gb_GenCxxObject_get_source,$(2)) : | $(call 
gb_LinkTarget_get_headers_target,$(1))
-$(call gb_GenCxxObject_get_target,$(2)) : T_CXXFLAGS += $(3) $(CXXFLAGS)
+$(call gb_GenCxxObject_get_target,$(2)) : T_CXXFLAGS += $(3)
 
 ifeq ($(gb_FULLDEPS),$(true))
 $(call gb_LinkTarget_g

Re: 4.2.0: Build for ARM

2017-11-28 Thread Peter kovacs 
What's the category for those?

Am 28. November 2017 08:42:17 MEZ schrieb Damjan Jovanovic :
>Raspberry Pis?
>
>On Tue, Nov 28, 2017 at 9:41 AM, Peter kovacs  wrote:
>
>> Maybe the patch is interesting to AndroOffice? Anyone from them on
>our
>> list?
>>
>> In general I'd say that we need a different gui for touch screen
>devices.
>>
>> The other case is I can think of ARM processors is arduino machines
>with
>> Linux installed. Don't know if this is a use case at all.
>>
>> Am 27. November 2017 23:46:27 MEZ schrieb Marcus
>:
>> >Am 24.11.2017 um 23:16 schrieb FR web forum:
>> >> Here: https://bz.apache.org/ooo/show_bug.cgi?id=127040
>> >> Eric Bachard provide a patch to build AOO on Linux ARM (32 bits).
>> >>
>> >> Maybe a good point for next 4.2.0?
>> >
>> >I don't know how relevant the ARM architecture still is and if an
>> >office
>> >suite is useful for it. However, someone needs to take care of the
>> >ability for building on this platform. A patch is nice but is not
>> >enough
>> >for future changes within the whole code base.
>> >
>> >My 2 ct
>> >
>> >Marcus
>> >
>> >
>>
>>-
>> >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> >For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>

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