History

Stephan Bergmann 1101b3524d Repurpose regcompare test as unoidl-check test `532b47a650` "[ABI CHANGE] In SDK, replace regcompare with unoidl-check" had left "registry/CustomTarget_regcompare_test.mk around to verify that unoidl-check behaves the same as did regcompare on those old-format .urd/.rdb files." Behavior of unoidl-check on those old-format .rdb files will become less relevant with the planned move from the old-format idlc/regmerge toolchain to the new-format unoidl-write toolchain also for the SDK. But there appear to be no unit tests for unoidl-check, so repurpose (and move around) the existing test (switching it from using idlc/regmerge to using unoidl-write). Change-Id: I4c33e9c16aaf0f99e35d9257a40f3bc2ae2725ea Reviewed-on: https://gerrit.libreoffice.org/c/core/+/121783 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>		2021-10-15 07:59:25 +02:00
..
inc
source
test
tools
Executable_regmerge.mk
Executable_regview.mk
IwyuFilter_registry.yaml
Library_reg.mk
Makefile
Module_registry.mk
README.md
StaticLibrary_registry_helper.mk

README.md

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.