Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ic6ad3e2c7f69dd123077a913f35f1971f1e8ca13
|
|
Change-Id: I1240656cc2a4d713c838eb80fa90ce3485aad614
|
|
Change-Id: I09534eab67c0ae38cd6965c3b63227d92b72c646
|
|
...but only in those parts of registry B that are not also in registry A. That
way, we can detect newly introduced violations while ignoring the old
(published) violations for backwards compatibility.
Change-Id: Ifb8ea98fffca29647aa6677a5ade86e5b194ddee
|
|
...mostly done with a rewriting Clang plugin, with just some manual tweaking
necessary to fix poor macro usage.
Change-Id: I71fa20213e86be10de332ece0aa273239df7b61a
|
|
It's not very efficient, because we generally end up copying it twice -
once into the parameter and again into the destination OUString.
So I create a clang plugin that finds such places and generates a
warning so that we can convert them to pass-by-reference.
Change-Id: I5341a6ea9e3190f4b4c05c42c85595e3dcd83361
|
|
Fixes:
no match for ‘operator!=’ in ‘i != std::vector<_Tp, _Alloc>::rend() [with _Tp = rtl::OUString, _Alloc = std::allocator<rtl::OUString>]()’
Change-Id: I7b4ba07ebe51c73893a3d6b77dcf5681b7638efb
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>
|
|
- the CustomTarget seems to be a test, not a build target
- worse, it is .PHONY
- ... and eats 30% of the top-level build-nocheck time alone
- so hopefully, we can we at least make it a check target
Change-Id: I113777cbd849aab9e8d0a77184e31194bc07232e
Reviewed-on: https://gerrit.libreoffice.org/8111
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
Tested-by: Stephan Bergmann <sbergman@redhat.com>
|
|
Change-Id: Ie6f5f2a634171d9618f3229bcc18ad48fff80d35
|
|
Change-Id: Ia5f104bfd707bcf4e159c78ca2764c861fb0b6d9
|
|
Change-Id: Ie708de4a7fbd34e1ab3c417688de79d5bdf0e0b8
|
|
Change-Id: Ifa19a427543e76053e9b249c479e1e13f3599bcc
|
|
Change-Id: Iab32e6974a181e437630aaae2ea73eb6062ec0ee
|
|
Change-Id: Icd47d87f93641a0b24a96a4be8d3d120f0405f2d
|
|
...and enable tests shared with idlc
Change-Id: I422b16c9b2636835d276cc2085cb640073894c97
|
|
Change-Id: Ib7ee3188b87b9b4216214b65347e34970e1b92a5
|
|
Change-Id: I7faa689c803f83687cfcc39dc7c4fd145584e849
|
|
Change-Id: Icd156745da10011611590b6b62cd0ec2df2b1266
|
|
Change-Id: I93b9fcc2b20ed7a7c160a9ef3294b6e578678f53
|
|
Change-Id: I8fb3c25cd583b688104a0ee8620696e7b2958ab5
|
|
Otherwise cppuhelper::TypeManager::createTypeDescriptionEnumeration, sitting on
top such an AggregatingCursor, will miss any entities from provider P' in module
M if any previous provider P contains the same module M.
That happened when climaker generates cli_oootypes.dll, where the enumeration
missed everything from offapi in top-level module "com" because it had already
seen udkapi's "com", and only reported the handful of entities under offapi's
other top-level module "org" (which does not appear in udkapi).
Change-Id: If538391bde22bcc346417b5988cf12023f0d4172
|
|
...as there are many cases where the code later wants to obtain this part, and
esp. for the string literal variants it is awkward to calculate the length of
the literal again if this is coded with a following copy() call. Adapt some
code to use this new feature.
(Strictly speaking, the @since tags for the---backwards-compatibly---modified
functions are no longer accurate of course. Also, clean up some sal_Bool and
SAL_THROWS(()) that are unnecesssary cargo-cult here, and where the clean-up
should have no practical compatibility consequences.)
Change-Id: I43e5c578c8c4b44cb47fd08f170b5c69322ad641
|
|
Change-Id: I5e1d870a60f4c0d4b805c615d0e3c958e856bf8c
|
|
...instead of a warning, now that all the deliberate changes have been
addressed.
Change-Id: I6075a36a560bd68826c6840992eefb8f51b939ba
|
|
Change-Id: I62af395105f51e802b874424b993dcf7e687a78b
|
|
Change-Id: Ie81e9994084b5a2f44a436c764318ea6e5049faf
|
|
Change-Id: I0fb4ca4e529f5f35e3619bab5e89348dd9c67faf
|
|
...via unoidl-write and the new source-format registry provicers, instead of
using idlc to produce .urd files, regmerge to merge them into legacy .rdb files,
and unoidl-write to translate those to new UNOIDL .rdb files.
gb_UnoApi and gb_InternalUnoApi ctors take an additional argument now that is
the path (below $(SRCDIR)) of the source-format registry from which to obtain
UNOIDL entity definitions. It can either be an .idl file (in which case no
*_add_idlfiles calls should be used and the resulting .rdb will contain all the
entities from that one .idl file; used in some tests to conveniently define all
test-specific entities in a single file) or a directory denoting the root of an
.idl file tree (in which case *_add_idlfiles calls specify the entites to
include in the resulting .idl file). (In the first case, the generated .rdb
file needs to depend on that single .idl file, so the gb_UnoApiTarget ctor
contains a dependency on that additional argument, which happens, as a side
effect, to trigger rebuilds in the second, tree-based case when addition/removal
of .idl files in the tree causes updates of directory time-stamps.)
UnoApiPartTarget and all the dependency-tracking logic based on .urd files in
solenv/gbuild/UnoApiTarget.mk is gone. Generation of an .rdb file now depends
on its source registry (see previous paragraph) and all the .idl files specified
with *_add_idlfiles (in the second, tree-based case above).
A consequence of that is that gb_UnoApi_add_idlfile, -_nohdl, and -_noheader all
do the same now. I left them in for now anyway, maybe they become relevant
again when the use of cppumaker is changed to read directly from a source-format
registry instead of going via a .rdb registry.
The legacy tools idlc, regcompare, regmerge, and regview are still contained in
the URE or SDK for now.
cb344cd59e1ddb7c6db66dbd9263b4755969d4ba "Revert 'Looks like idlc resolved
typedefs inside sequence<...>'" is re-reverted as now "the current offapi.rdb is
generated via unoidl-write instead of idlc."
Change-Id: I3d9d92f17326bc9f49dd934c85aab6a17951d06d
|
|
Change-Id: Ib4cc138ab4c6de0d3d3a8ad55e40ba9ca30c15ae
|
|
Change-Id: I7814547ef29ec728a5a815196427b661bf285256
|
|
Change-Id: I331d769132d3b18c870c70c7abcbd9539135af55
|
|
Change-Id: Ia40f0ce43086fd73cba60011001640a945fb3e26
|
|
Change-Id: Ia3d8931341b2d47ef76265d94410d83f51a068c0
|
|
Change-Id: I79660ddd3ec9f78452fa484b33a9720cbf8ddc80
|
|
...for checking compatibility with the reference rdbs. unoidl-check is no
longer based on the legacy registry format, but can process all the various new
UNOIDL registry formats. regcompare is still included in the SDK for now.
(gb_UnoApi[Target]_set_reference_rdbfile now takes a non-empty sequence of rdb
files, any necessary dependencies of the final rdf file preceding it just like
it is required on the unoidl-check command line. Also, executing the
unoidl-check now properly depends on those rdb files.)
TODO: unoidl-check is too conservative for now and flags some changes as
incompatible that are not.
Change-Id: I92e4c69403c5e3fcb31707c98c65a2f509592dd4
|
|
Change-Id: I206b623fcc3c9e04fc5336cb3704315c44fb83b8
|
|
Change-Id: I2d71e148f302ebfbf8d0fbfc74a7fb523b7bfcd4
|
|
Change-Id: I8299079b46be4ccb7070f5497d089166a953c939
|
|
Change-Id: Id1edf4fcebfe0d839162adb442695e9ce39e3f75
|
|
Change-Id: I93d35ca7b784fc6d1b228347053ef0f76904f039
|
|
Change-Id: I784ba245526f6fbf933ee485df1604e82980d931
|
|
Change-Id: I7475114158d64b8dbe64cd9d1de3415454c762f4
|
|
Change-Id: Ibd6ce23d2698280105469fb75c4afa225dc237ee
|
|
Change-Id: I7d8b196d047b1e0075acdbf380a9b3ed750a7b90
|
|
The Bison 3 generated sources do not seem to define YYID, so our
YYLLOC_DEFAULT definition was broken. No idea what any of this means,
but sberg said I can safely remove the YYID usage, so if it kills your
pet, you know whom to blame.
Change-Id: I464564be941e0a49da264057923bf8e8e82d5ffd
|
|
Change-Id: Ia344d5a68118ba9896672ebbf4cccaf0511f8186
|
|
Change-Id: Iab795a34a657cb36ced24a1a05f6c21a6c1637aa
|
|
Change-Id: Ic864f9c6f3dbbe9f75bdae76818c00f62825182d
|
|
...in preparation of SourceFile- vs. -TreeProvider.
Change-Id: I4c8f37ade1ba26cb7b38f63211711613d1b98a73
|
|
Change-Id: Ifc8d95b4b15a7dd91195e6f727fdb7fa2a267be9
|