cbea5d30b9
...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 |
||
|---|---|---|
| .. | ||
| source | ||
| test | ||
| tools | ||
| workben | ||
| Executable_regcompare.mk | ||
| Executable_regmerge.mk | ||
| Executable_regview.mk | ||
| Library_reg.mk | ||
| Makefile | ||
| Module_registry.mk | ||
| README | ||
| StaticLibrary_registry_helper.mk | ||
Registry reading, etc. This provides tools for dealing with the legacy binary types database format, still in use by extensions and the core code. While the actual binary file format is implemented by the [[store]] code, the wrapper that turns this into a type registry is implemented here. While this code is primarily used in only two modes: * linear write / concatenate * random access read The API unfortunately exposes a random-access write approach, which - while ~unused needs before we can re-write this away from the store backend.