| Age | Commit message (Collapse) | Author |
|---|
|
* all .ui files go from <interface> to <interface domain="MODULE"> e.g. vcl
* all .src files go away and the english source strings folded into the .hrc as NC_("context", "source string")
* ResMgr is dropped in favour of std::locale imbued by boost::locale::generator pointed at matching
MODULE .mo files
* UIConfig translations are folded into the module .mo, so e.g. UIConfig_cui
goes from l10n target to normal one, so the res/lang.zips of UI files go away
* translation via Translation::get(hrc-define-key, imbued-std::locale)
* python can now be translated with its inbuilt gettext support (we keep the name strings.hrc there
to keep finding the .hrc file uniform) so magic numbers can go away there
* java and starbasic components can be translated via the pre-existing css.resource.StringResourceWithLocation
mechanism
* en-US res files go away, their strings are now the .hrc keys in the source code
* remaining .res files are replaced by .mo files
* in .res/.ui-lang-zip files, the old scheme missing translations of strings
results in inserting the english original so something can be found, now the
standard fallback of using the english original from the source key is used, so
partial translations shrink dramatically in size
* extract .hrc strings with hrcex which backs onto
xgettext -C --add-comments --keyword=NC_:1c,2 --from-code=UTF-8 --no-wrap
* extract .ui strings with uiex which backs onto
xgettext --add-comments --no-wrap
* qtz for gettext translations is generated at runtime as ascii-ified crc32 of
content + "|" + msgid
* [API CHANGE] remove deprecated binary .res resouce loader related uno apis
com::sun::star::resource::OfficeResourceLoader
com::sun::star::resource::XResourceBundleLoader
com::sun::star::resource::XResourceBundle
when translating strings via uno apis
com.sun.star.resource.StringResourceWithLocation
can continue to be used
Change-Id: Ia2594a2672b7301d9c3421fdf31b6cfe7f3f8d0a
|
|
Change-Id: I390b97bbacfc123b952be2b54cf1333b4d5c24a7
|
|
Change-Id: Ibf06e37acc4b6ea69863abc9267152278c4598be
Reviewed-on: https://gerrit.libreoffice.org/35770
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Tested-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
|
|
Up to now the screenshot creation was added/dependent of
target slowcheck. Since quite some modules have added screenshot
creations now, I added an own target 'screenshot' to allow to keep
current slowcheck and screenshot creation separated
Change-Id: I80a49a0db607edf8e0405672d570f624d29912e7
|
|
using the gb_DBGARGS variable.
This value is appended to the gdb "set args" command.
Change-Id: Ic15754d7edcc448f283522338900684a29a03cf3
Reviewed-on: https://gerrit.libreoffice.org/21364
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
Tested-by: Jan-Marek Glogowski <glogow@fbihome.de>
|
|
Change-Id: I10d30097a7e7099d43a6760489dcbbf405828960
Reviewed-on: https://gerrit.libreoffice.org/20267
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Tested-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
|
|
Change-Id: I6e65f70848eb466c7c08fcffb478a2963b91cdb6
|
|
Change-Id: I17ebccb268e317346ca05d6a112ec33357684876
|
|
Change-Id: If389e2dc6f5af07662e6ab8aa94e0e9ce8e30f5b
Reviewed-on: https://gerrit.libreoffice.org/19865
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Tested-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
|
|
Change-Id: I4d1e54bdf579b0d6dd143b3a68de259ab7d3d562
|
|
Looks like following GNU build system standards isn't necessarily the
best idea, if even the documentation gets it wrong.
Also document the ENVCFLAGS/ENVCFLAGSCXX variables.
see also: i#116959 and:
http://www.gnu.org/software/autoconf/manual/standards.html#Command-Variables
Change-Id: I56d8623cbbc800ef80da1610f6fd104ac29beaf9
|
|
This was unused since the earlier cleanup.
Change-Id: Ia56641c4242037a0ce501e43939b8dc862499f0e
|
|
Change-Id: Iaee342ae6d612e35d1d2dfa91edbc952d4f73b4e
Reviewed-on: https://gerrit.libreoffice.org/11616
Reviewed-by: Matúš Kukan <matus.kukan@collabora.com>
Tested-by: Matúš Kukan <matus.kukan@collabora.com>
|
|
Change-Id: I096798159f4d3d59306be1b3843de1daca280f7a
Reviewed-on: https://gerrit.libreoffice.org/11342
Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>
|
|
Run them with "make perfcheck" (toplevel or in a module)
To add a new performance test:
- Add it as a perfcheck target
- Use gb_CppunitTest_set_performance_test
- Use CALLGRIND_ macros from valgrind/callgrind.h
http://valgrind.org/docs/manual/cl-manual.html#cl-manual.clientrequests
Change-Id: I67c776dbe4db0a686607efeee7a7e4f3aeae0e5c
|
|
Corrected typo, included the option dump-deps-png because that is
awesome and available and not in this helpfile! :-)
Change-Id: If8dd8b9c4dc9938c65499ae5d6dfdd7bf830e94d
Reviewed-on: https://gerrit.libreoffice.org/8747
Reviewed-by: Chris Sherlock <chris.sherlock79@gmail.com>
Tested-by: Chris Sherlock <chris.sherlock79@gmail.com>
|
|
For those who use the 'make help' paradigm to look for an entry point to
how to run their tests.
Please see this commit for context:
4e887567c5b4b06646ab1340376e240d6c5af9cb
Change-Id: Id7ffed3aa1e5157406c0c3d5328f4dd5b7d81178
Reviewed-on: https://gerrit.libreoffice.org/8155
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
... UserInstallation in test-install/ does not make sense.
It already has this: instdir/program/bootstraprc:UserInstallation=$ORIGIN/..
Change-Id: I0d5e952876b80661375cc5ca6f8fbf44539bc83f
|
|
... it is an abbreviation of "Solar Version".
Since nobody can remember that:
remove OUTDIR OUTDIR_FOR_BUILD SOLARVER SOLARVERSION solarpath
and any mention thereof.
Change-Id: Idb3031c4f25a76ac05b22ec67e3ca3e1e8e512ad
Reviewed-on: https://gerrit.libreoffice.org/6515
Tested-by: LibreOffice gerrit bot <gerrit@libreoffice.org>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
|
|
Change-Id: I488def80e855624ffd85a0b6c4cc19819c39ed01
|
|
Change-Id: I9e4e153e1a9ac82d4015b73ecf3a9a2429ab346f
|
|
Change-Id: I032f9737746b39047b2d62df6821da4b3b9e9242
Reviewed-on: https://gerrit.libreoffice.org/3395
Reviewed-by: Joren De Cuyper <joren.libreoffice@telenet.be>
Reviewed-by: Jan Holesovsky <kendy@suse.cz>
Tested-by: Jan Holesovsky <kendy@suse.cz>
|
|
- deliver was only relevant for dmake
- showdeliverables works only per-module
- "'showmodules' is now pointless, it was used to identify modules from
tail_build"
[<http://lists.freedesktop.org/archives/libreoffice/2013-February/046510.html>
"Re: Show module dependencies"]
Change-Id: I400ec5bed4397a12ce4c5b604253c74ef7de0ce7
|
|
Change-Id: I8b746c3786eda42c3c91c104daee2018ba20b975
|
|
When compiling using a PCH, includes included using the PCH usually don't
show up in compiler dependencies output, so the only the PCH has a dependency
on the include, and the source has only a transitive dependency. Switching
to non-PCH (e.g. ENABLE_PCH= on cmdline) means the dependency is lost.
Trying with the PCH timestamp was a nice try, but it can sometimes still
miss something. So whoever wants to switch needs cleaning first or
just know what they're doing.
|
|
Change-Id: I6b650781b11163eb99828d0d933ae9a38e0e09fa
|
|
This is mostly a revert of 992757cc5ebfb1df42636b8d3269cdbc10fc4148
and bc78ac68c2492e63a680f68b524c4a51179ea83e, with tweaks to apply.
Also only MSVC support for now.
Change-Id: Ia926b3c28125b52012156ccfd47932837b09d20a
|
|
Currently there are 4 different debug options:
--enable-dbgutil (the recommended one)
--enable-debug
--enable-selective-debuginfo
--enable-symbols (for advanced users only)
In this table the properties of each option is shown:
----------------------------------------
options\properties | O | S | D | T | U |
----------------------------------------
production-code | x | - | - | - | - |
----------------------------------------
--enable-symbols | x | x | - | - | - |
----------------------------------------
--enable-debug | - | x | x | x | - |
----------------------------------------
--enable-dbgutil | - | x | x | x | x |
----------------------------------------
where
O: optimization
S: debug symbols
D: debug STL
T: trace facility
U: additional debug utility (object counting)
Note:
--enable-selective-debuginfo has the same properties as --enable-debug
Change-Id: Ib8a28c6162f47526d6bb33f81f53835cd11894b2
|
|
Change-Id: I30c9700127d04aee200386c94307a45da41b0025
|
|
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: I55257cc5dbdffdc2dd9f9222a120f0a322dda7c8
|
|
Change-Id: I5a692b10f259cf95357b1b3da39e0cbc8e68c044
|
|
Change-Id: Id3c206219385d6ab4673d1c8f6236a6cb665512a
|
|
Change-Id: Ie94ba4b3a774ab947574c74837ecbc932bb3b621
|
|
|
|
This somehow fell through the cracks of gbuildification -
make timelog=t now again enables those RTL_LOGFILE_ macros.
|
|
|
|
|
