office-gobmx/registry
Michael Stahl ba8372449b registry: new ZipPackage_registry_odk_headers
Change-Id: I0730e0a354ec952cdb67d1b22067ab59c86334c0
2013-02-27 01:33:19 +01:00
..
inc/registry
prj
source
test
tools
util
workben
Executable_reg2bin.mk
Executable_regcompare.mk
Executable_regmerge.mk
Executable_regview.mk
Library_reg.mk registry: new ZipPackage_registry_odk_headers 2013-02-27 01:33:19 +01:00
Makefile
Module_registry.mk registry: new ZipPackage_registry_odk_headers 2013-02-27 01:33:19 +01:00
README
StaticLibrary_registry_helper.mk
ZipPackage_registry_odk_headers.mk registry: new ZipPackage_registry_odk_headers 2013-02-27 01:33:19 +01:00

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.