Age | Commit message (Collapse) | Author | Files | Lines |
|
that are needed to load .odt, .sxw etc files, and
add a regression test for CVE-2012-4233
Change-Id: Ie178725ded3d76942030d12f23074de519cf62de
|
|
Change-Id: I1dda0f2b3bc2bb4a4a877c160026e53a90471d54
Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
|
|
Change-Id: Ief6d6678a04084a90d07d87780689b92af2e3ba4
|
|
Change-Id: Ia1b6830ef9ab06a1914abb7f6d5857ce9d845061
|
|
Always link in gb_STDLIBS, except when the library explicitly opts out
with gb_LinkTarget_disable_standard_system_libs.
Change-Id: I489a99114fbfa46d0421a27cf6c7b899dc268a4a
|
|
add a new gb_LinkTarget_use_system_win32_libs to abstract different
linker options on MSVC and GCC.
Change-Id: Ic9bf2545f59bf7871e6fc06b290c486ddfbec03d
|
|
... new gb_LinkTarget_add_standard_system_libs
Change-Id: Ib2bc843098db3d8c6822b45a3d21724e67f57d69
|
|
Change-Id: I53316e0b9369d806197bccb42cf22d3497af43e7
|
|
* As UCB is only ever initialized with "Local"/"Office", remove this
configuration vector completely. The "create" ctor creates an instance
internally initialized with those "Local"/"Office" keys. Special (test) code
can still instantiate an uninitialized one via plain createInstance. And for
backwards compatilibity process startup still ensures to create an initialized
instance early, in case there is still code out there (in extensions) that
later calls plain createInstance and expects to get the already-initialized
(single) instance.
* XInitialization is an "implementation detail" of the UniversalContentBroker
service, do not expose in XUniversalContentBroker.
* ucbhelper/configurationkeys.hxx is no longer needed and is removed.
* ucbhelper/contentbroker.hxx is an empty wrapper and is removed; however, that
requires ucbhelper::Content constructors to take explicit XComponentContext
arguments now.
* The only remaining code in ucbhelper/source/client/contentbroker.cxx is
Android-only InitUCBHelper. Is that relevant still?
Change-Id: I3f7bddd0456bffbcd13590c66d9011915c760f28
|
|
Change-Id: I3afe59a6326b9e5cb26c39a82d7aabdb05cc2b7e
|
|
Change-Id: I1f9341d1b70b9b996f3b344433e949647e12edf6
|
|
Change-Id: I265e0fddc12a40cff0b6a6172bfca96eda0842ec
|
|
Change-Id: If468ca444865f81a7adeabb72ecb6d8647f6dde0
|
|
Change-Id: Ib74b96200c9d57f55fc0d32b638601c64e7eb6fe
|
|
Change-Id: I6b0cf900003beb9931d6acad229166e44cc7f0bc
|
|
|
|
Change-Id: I14cab3dfd26ac1568feef902b566873cecf049b9
|
|
Use ksc5601.h header from XFree86 Project Inc. Patch contributed by
Oliver-Rainer Wittmann with minor changes from Pedro Giffuni
http://svn.apache.org/viewvc?view=revision&revision=1179296
|
|
Change-Id: I8018d9b5fa01d1720c0392dc5fdc4a0656f25a35
|
|
Change-Id: I6c145e984c885c7e06caa1c27bfb354ea49ad9ce
|
|
Change-Id: Ic24e9b98b1c6e868061caa911865ce2267bdcfaf
|
|
this removes dmake completely out of the build for migrated modules
build.pl now assumes modules to be gbuild, unless there is a
prj/dmake file
Change-Id: I674a036b182ee13c5ec093e83cb3d38133112d3b
|
|
|
|
|
|
and stick headers into the solver in the same hierarchy as is "standard"
so we don't have to patch so much, similiarly rename to libz
|
|
|
|
|
|
|
|
There are unit tests that do not use URE, e.g., in cppuhelper.
This reverts commit 33e9f3d3d6b29545ef9df3f5334c015e15caa5c8.
Conflicts:
sot/CppunitTest_sot_test_sot.mk
svl/CppunitTest_svl_urihelper.mk
|
|
|
|
|
|
|
|
|
|
Or is there any use case where we would need to use UNO API headers, but
not require the appropriate type database at runtime?
|
|
Naming convention for gbuild methods:
- "add" is used for stuff that is logically a part of the target
(i.e. not registered at the Module, but defined in the target's makefile)
- "use" is used for stuff that is logically a different target
(i.e. it is registered at the Module, has it's own makefile, may be
in a different module than the target)
|
|
|
|
They should not need any actual UI anyway, and most of them already
pass the option manually.
http://lists.freedesktop.org/archives/libreoffice/2012-March/029109.html
|
|
Otherwise there's a build dependency missing (and it's apparently
not needed anyway).
|
|
|
|
The real reason for this change is that clang aborts with a fatal
error in backend (http://llvm.org/bugs/show_bug.cgi?id=12226),
but I'm not sure whether this was a correct construct in the first
place anyway. The contents are above 0x7f, which may be outside
the range of plain char, if it is signed, so maybe the result is undefined.
I don't want to spend the time checking in the spec,
but this new variant is technically the same and it is safe.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|