12353c7386
Add LegacyProvider to read the old format (requires a provider Manager, to resolve singletons' bases, to decide whether they are interface- or service- based). Replace registry-based reg2bin with provider-based reg2unoidl. Change-Id: I5865e62308cc2d9c5439211ac803d84e93aab656 |
||
|---|---|---|
| .. | ||
| inc/registry | ||
| prj | ||
| source | ||
| test | ||
| tools | ||
| util | ||
| workben | ||
| Executable_regcompare.mk | ||
| Executable_regmerge.mk | ||
| Executable_regview.mk | ||
| Library_reg.mk | ||
| Makefile | ||
| Module_registry.mk | ||
| README | ||
| StaticLibrary_registry_helper.mk | ||
| ZipPackage_registry_odk_headers.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.