| Age | Commit message (Collapse) | Author |
|---|
|
This allows us not to have cups during the build time of libreoffice.
Commit is inspired from patch from Dave Flogeras <dflogeras@gmail.com>.
Change-Id: I I32a14eb6e7bdd13de1a737d4798c852a830ae326
|
|
|
|
Change-Id: I6a178f7ff9c8306e15bcfa847ad1e5e4f8476504
|
|
make 3.82 understands mixed paths, so use them.
This allows us to get rid of evil in BuildDirs.mk.
Hopefully, life will be simpler now.
Change-Id: I I I641f28c6af1948963f7004f8071af62e21caabb3
|
|
|
|
Change-Id: I4ac3e017f1450a14d2bb389b72ffd2e69cc5767a
|
|
OOo used to use debug level this way:
0 is default for product build
1 for --enable-dbgutil
2 for environment variable debug=t, regardless of dbgutil setting
in LO these have now morphed into:
0 is default for product build
1 for environment variable debug=t
2 for --enable-dbgutil (at some intermediate stage in the past)
1 for --enable-dbgutil (today)
This has caused a lot of confusion and some things were not converted
properly, including a check in LinkTarget.mk.
Developers should use --enable-debug to get useful information,
including full debug info and assertions.
--enable-symbols is not intended for developers, but for people
who need their builds to be able to produce useful stack traces;
--enable-symbols is for example set unconditionally in the Fedora RPM
spec, and for this purpose disabling of inlining is not wanted.
It is unlikely that somebody wants symbols for only part of the build,
and consequently a different mechanism is used to set the corresponding
flags: they are set into global gb_LinkTarget_C{,XX}FLAGS.
So move the selective symbol feature back to --enable-debug.
(this substantially reverts db8df57acd601ed084bd0122683e1bd066a4f143)
|
|
It is done the same way the beanshell is handled.
Currently it can't be enabled by default as internal version has
patched-in debug interface.
We can choose two paths, rewrite the code to the new rhino debug
interface or just strip the current one out.
Change-Id: I48af18c635816db8269f13a649b62e9c454ee1e6
|
|
If you'd use it, you'd get icons from fallback themes.
That I consider misleading.
Change-Id: I I Id1d71ef3f2e90f783d03ef8287f53f05ce4aa9a9
|
|
Change-Id: Ie8987092a63e9a3b5d3b94f7ae54fbef98fdfc2c
|
|
Do not install the benashell/javascript stuff if they are not actually
bult.
Build rhino only when required by javascript extension.
Change-Id: Icc378524008389af35631c64a1a0288eb4f271be
|
|
Also add galaxy to known list as it is pseudo alias for default.
Change-Id: I5c1175a950319e73da29e77daca9243f165243f1
|
|
Also sort all the others alphabetically.
By the default the provided themes are same as on 3.5, otherwise
user can specify each of the available ones.
This avoids use of --with-theme=default which then produces warning
"no such file or directory default" by using the proper theme name
(ie. galaxy) which does not produce this.
There is no visible difference on:
--with-themes=galaxy or --with-themes=default
Change-Id: I I1a6409f55fdfdff6a19781b25627dcb7682b0fb7
|
|
Change-Id: I1d3ade7813f85c3d87ba2e5017e9635d663ef76a
|
|
|
|
Change-Id: I7d5d8e380e12cc66255ddc3ac3f70bab7713f8b6
|
|
Signed-off-by: Petr Mladek <pmladek@suse.cz>
|
|
|
|
Or maybe it's the Mach-O object file format that lacks the
functionality? Anyway, let's try to manage without visibility then.
|
|
For unrecognized options, Clang 3.1 (and ealier?) prints out a
warning, but it isn't a real warning as it doesn't cause a compilation
error with -Werror, so it is impossible to find out reliably if an
option is supported or not. So hardcode the information we know.
|
|
|
|
|
|
Do not depend on a distro-configs file to disable it. It is supposed
to be optional to pass a --with-distro option. Running a bare
./autogen.sh is supposed to produce a working configuration.
|
|
|
|
|
|
|
|
CLucene apparently does not bother with self-contained headers
|
|
Maybe they'll be supported somewhen in the future, so do not hardcode
them out. Also, gb_DEBUG_C(XX)FLAGS are apparently common GCC options,
not platform-specific.
|
|
|
|
the argument given now can
- be 'all', meaning everything
- start with -, meaning not to enable symbols for that item
- end with /, meaning everything in that toplevel directory
- be a target of the form targettype_name, e.g. Library_swui
Note that there is no ordering and removal takes precedence.
|
|
- move using optimization, symbols (i.e. debug) and environment
cflags/cxxflags into one place
- --enable-dbgutils is independent from --enable-debug, and thus
also --enable-symbols, so it should not set debuglevel
- setting -g flag is controlled by --enable-symbols, not --enable-debug,
so it should be used also for selective -g enabling
- setting debug flags depending on debuglevel being 2 is certainly wrong
- do not let environment cflags/cxxflags disable optimization/symbols flags
completely, if one wants, it's possible to explicitly specify e.g. -g0,
but the current way does not make it easily possible to specify e.g.
-fcolor-diagnostics
- do not set debug flag globally now that it can be done selectively
|
|
|
|
|
|
Especially if it will be set as a result of the code that now tries
to use it (alternatively, it comes from the Qt3 check, which is not
right either).
|
|
|
|
|
|
|
|
|
|
|
|
Also, if /usr/share/hunspell doesn't exist, look for /usr/share/myspell
as well.
|
|
As the distros already had enough time to pick up the required patch and most did.
|
|
|
|
|
|
This reverts commit 844b4520a9f0879d7b756654cef8fdbaa03a9000.
|
|
|
|
Even if it does nothing because there is no installation available .-)
|
|
|
|
with this you can now do:
./autogen.sh --enable-debug="sw sc"
and your build will have debug version of the libraries sw and sc, but a
non-debug build elsewhere. This currently only works for libraries. It would be
also possible to extend that to excutables, but that would need explicit in the
enable-debug switch then:
./autogen.sh --enable-debug="Library/sw Library/sc Executable/mkunroll"
so I dont know if it is worth it.
|
|
|
|
|
