- gb_UnoApi_get_target returns the files in INSTDIR
- stop using rdb files from OUTDIR
- remove gb_UnoApi_install
- remove pointless 2nd parameter of gb_UnoApi_UnoApi
- order-only dependency from gb_UnoApi_get_target to
gb_UnoApiHeadersTarget_get_target because INSTDIR .rdb is always outdated
Change-Id: Id418f75e9b38d6fe135b55eca2594c2624bc41cc
...strictly speaking, such a change is incompatible, but in case of such a typo
it is probably best to do the cosmetic change anyway.
Change-Id: Ia4f773676addff5bfa64817ac724fa27c61b2a4b
...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
...obtained from the old .rdb files via "unoidl-read --published". This removes
the need for update-rdb.sh.
Change-Id: I73c0d026af7e27370602f83c61dfa76fc4d17a83
...doxygen still picks them up, as it traverses the complete udkapi/ and offapi/
soruce trees. (And rename udk-modules.idl to modules.idl for consistency.)
Change-Id: Ic52c333756810c285059f03edc207a0913ead160
UNOIDL identifiers starting with a lowercase letter and containing hyphens are
reserved for the implementation. It would be good to be able to enforce that in
code parsing UNOIDL files, but some existing identifiers violate that.
In the case of the published, deprecated css.uno.Uik, the change is incompatible
in theory but arguably irrelevant in practice.
Change-Id: I61f66e2d73c6aca5498ae566758893b546eb81d5
Only useful ones appear to be <tbody> and <thead> which doxygen doesn't
support but we only use those in 3 places so who cares.
Change-Id: I374f7d208873a8436fe76e0f800ce18df5b188b3
<listing> is called @code / @endcode in doxygen.
@example requires a file name in doxygen.
Also adapt various silly examples that use tools String in C++ or manual
syntax highlighting in Java etc.
Change-Id: I23cff1b688001f438526a6a1364cc5f754b504f7
It is amazing what some people believe autodoc supports.
Also, com::sun:⭐:uno::Any does not exist in IDL, that is part of
the C++ language binding.
Change-Id: I1f1f5cf5d27663ace6ff618ecbecb41fd2dfa1fc
What is sad about this is that autodoc doesn't even support <method>.
sed -i "s,<method>\([a-z][^<]\+[^)]\)</method>,\1(),g"
Change-Id: I702ef71423ced1d5195f2e0535e73b1bb4d3f6f2
This one is apparently often abused to link to a constant group, while
it can only link to constants within a group.
sed -i "s,<const>\([^<]\+\)</const>,\1,g"
Change-Id: Ic3d8099751340e4b046298c861bb659beb351eaf
Doxygen would probably recognize these without () too but add them for
consistency.
sed -i "s,<member>\([^<]*::[a-z][^<:]\+[^)]\)</member>,\1(),g"
Change-Id: I2615b99265b75633459e35164e54d9da7fe76b85
Doxygen will only recognize a un-qualified method name as such if it is
followed by "()".
sed -i "s,<member>\([a-z][^<]\+[^)]\)</member>,\1(),g"
Change-Id: I69bc17849e76f3a3d91c6daf0f1be8168a83cfc5
Doxygen does not know type element and will recognize strings that
contain capital letter (all API types do) automatically as type.
This patch removes 15k doxygen warnings.
git ls-files | grep \\.idl | xargs sed -i "s,<type>\([^<]\+\)</type>,\1,"
Change-Id: I45c07cf0b115d5fb5353f4aa9719839615ea1150
