| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit d4ea8c6b7ee32dfbe1525cae45ad44d411052c33.
Change-Id: I85dacbf962cf5911c826c55fe08cfe6effe0e9d7
|
|
Define the functions that adds the various check targets as empty when
cross-compiling. Avoids the needs for corresponding conditionals in
.mk files in modules.
Change-Id: Ia577e12204b516dc169a8500b4745aac4d7c24e2
|
|
$(lastword $(MAKEFILE_LIST)) is not what is expected if the makefile
includes other makefile as the first step (as some do). See
UnpackedTarball.mk, where I already tried to workaround the problem.
Change-Id: Ib713a698f52ba16f46fbbc4c50b43edd69c9a472
|
|
Now we build only what we really need for 'build' platform - there is
new build-tools make target.
The list of tools is in solenv/gbuild/extensions/pre_BuildTools.mk.
Also similar is done to some extent for 'host' platform using
gb_Module_add_targets_for_build which is ignored for 'host'.
Change-Id: I6acd1762b16aca366aac1a0688500f27869cfca2
|
|
For both build and host platform.
Change-Id: I0fa9b5d85449887c2c6bd758fb1fecec9776d97c
|
|
Also kills horrible SKIP_TESTS hack along the way.
Change-Id: Ida59fb44d247b52ef11ee7ba5e4e006996a87ebf
|
|
Change-Id: Iffbe6d4570bf4d4bdd7347260a6bb4160af24515
|
|
Change-Id: Ib8d2ddb2efaef26a0a2aba36e9e1c67b1fb019d7
|
|
Change-Id: I06783d26f10efabd1aca06a7a1e0647d8ed58b69
|
|
Change-Id: I857ae6055326e43ad687ac22a6e4a034de5d556f
|
|
Change-Id: Ic192b063a4ccc1249194bc7a62a8a90682de08f0
|
|
Change-Id: Ie4deddc426356636b76ad4fc27552c6d3a1dd815
Reviewed-on: https://gerrit.libreoffice.org/2429
Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Tested-by: Caolán McNamara <caolanm@redhat.com>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I203ad92e8a006d1f262203852f05108706a90ee4
|
|
Change-Id: Ia6c938ef0e45ec86c0c202e95ef28d49fccd3497
|
|
Change-Id: Ib886a323c1ade6dcd455a44d3dfc6702086416e3
|
|
Change-Id: I5d00db54748de0e1ce3de3dd9c99a88a82e7917b
|
|
Change-Id: I5b53046e9389eac2126e910752d131e7b65bf53c
|
|
Moved from translations' custom makefile.
Change-Id: Ife58bfa3ee607b06617d7db80408afb453b9a10c
Reviewed-on: https://gerrit.libreoffice.org/1622
Reviewed-by: Miklos Vajna <vmiklos@suse.cz>
Tested-by: Miklos Vajna <vmiklos@suse.cz>
|
|
Change-Id: I09a6ad82bbb54ce8329e8b2f6152e9f5a1880a68
|
|
By default a product (non-developer) build is done. Code is optimized and no debugging
information is included (may be overriden though, see below).
Developers should preferably build with --enable-dbgutil , or at least --enable-debug.
The --enable-symbols switch has been removed. Use explicit CFLAGS/CXXFLAGS/LDFLAGS instead
if needed.
With --enable-debug optimizations are turned off and debugging information is included
(in order to make it possible to examine the code in a debugger). Additionally assertions
and logging is enabled (see SAL_WARN/SAL_INFO documentation for details and better control).
This switch should primarily by used for occassional development (such as when it is needed
to debug one module in a non-debug build, see also 'make DEBUG=true' below).
Using --enable-dbgutil is the recommended developer option. In addition to --enable-debug
it also enables additional checks, such as debugging mode for STL or checking compiler
plugins. This switch may also enable additional logging from obsolete debugging tools
(which should be converted to SAL_WARN/SAL_INFO for better control). Note that this option
makes the build binary incompatible from a --disable-dbgutil build, so it is not possible
to mix them.
When using --enable-debug/--enable-dbgutil , the build is noticeably larger because of the included
debugging information (compiler -g option). When disk space is an issue (or the computer
is not very powerful), the --enable-selective-debuginfo option allow specifying where
the debugging information should or should not be used. The option takes a list of arguments,
where all means everything, - prepended means not to enable, / appended means everything
in the directory; there is no ordering, more specific overrides more general,
and disabling takes precedence). For example, --enable-selective-debuginfo="all -sw/ -Library_sc"
enables debugginfo for everything except for anything in the sw module and the sc library.
Explicitly specified CFLAGS/CXXFLAGS/LDFLAGS override optimization and debugging options
(can be now also passed to configure which will make the build system use them).
If in a non-debug build it is needed to temporary build something as a debug build,
'make DEBUG=true' temporarily works as if --enable-debug was specified. It also temporarily
overrides debuginfo disabled using --enable-selective-debuginfo.
Old code using old logging functionality also has a concept of a debug level, forced using
'make DBGLEVEL=2'. Using a debug level of 2 (or higher) enables additional logging output.
New code should use SAL_WARN/SAL_INFO and use extra areas for additional logging output
that can be selectively enabled/disabled using SAL_LOG variable.
(Some smaller parts of this design will be implemented by separate follow-up commits.)
Change-Id: Ia6420ee3c99c217ead648e8967165eed7f632258
|
|
Change-Id: I3ac81132e21710a2c1d974944a5bcd612d796ec6
|
|
http://lists.freedesktop.org/archives/libreoffice/2012-April/029940.html
The RTL_USING #define (set by gbuild for anything that's not public
API) allows to use such classes simply by their name, without having
to use the namespace or do explicit using rtl::OUString (which half
of the sources do anyway).
Change-Id: I7edaf12cd278489cdc1d5ff782f0a86361c13c0a
|
|
This is convinient when coding/debuging stuff that break
unittest downstream, but oen still want to have a fully built
product to test
Change-Id: I4970db6ede1ed29bb3c421b56b5092c19fd9fa90
|
|
|
|
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)
|
|
The previous commit works but results in a ~0.4 second slowdown on
tail_build, which is completely unacceptable; seems that at the cost of
another ugly global variable in Module.mk we can get the performance back
and then some, so refactor this again...
|
|
so it doesn't use wildcard but instead the actually registered
LinkTargets.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- as long as we still have the slow build.pl run for top-level build
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
