On Friday 20 of April 2012, Lubos Lunak wrote:
On Monday 16 of April 2012, Bjoern Michaelsen wrote:
On Mon, Apr 16, 2012 at 01:50:00PM +0200, Lubos Lunak wrote:
Is it possible to do the build also the other way around, i.e. e.g.
"all but sc"?
Not yet, feel free to add it if you think it is essential.
...
and if I understand the change correctly, I'd have to manually
find out what all the dependencies actually are. Given that sc/sd/sw
are the biggest three, it probably even makes the biggest difference to
disable the two that one does not work on.
ALLBUTSCSW=`find . -name "Library*.mk"| sed -e 's/^.*Library_//' -e
's/.mk$//'|grep -v sc |grep -v sw` && ./autogen.sh
--enable-debug="$ALLBUTSCSW"
should be enough.
How about this?
And one more.
--
Lubos Lunak
l.lunak@suse.cz
From 42ef01bdc3b1e08ef90dc0d05d1d978b2085a088 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lubo=C5=A1=20Lu=C5=88=C3=A1k?= <l.lunak@suse.cz>
Date: Fri, 20 Apr 2012 17:26:01 +0200
Subject: [PATCH] if debug symbols are enabled indirectly, make sure they are
actually built
---
solenv/gbuild/gbuild.mk | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/solenv/gbuild/gbuild.mk b/solenv/gbuild/gbuild.mk
index 8e5141b..a37cb8b 100644
--- a/solenv/gbuild/gbuild.mk
+++ b/solenv/gbuild/gbuild.mk
@@ -105,6 +105,11 @@ endif
endif
ifneq ($(gb_DEBUGLEVEL),0)
+# if symbols are triggered by something else than --enable-symbols,
+# make sure they are actually enabled
+ifneq ($(gb_SYMBOL),$(true))
+ENABLE_SYMBOLS_FOR = all
+endif
gb_SYMBOL := $(true)
endif
--
1.7.7
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.