This section shows how to include the bundle support into an eCos configuration, and how to configure it once installed.
The bundle support is contained in a single eCos package CYGPKG_BUNDLE. However, it depends on the services of a collection of other packages for complete functionality.
Incorporating the bundle support into your application is
straightforward. The essential starting point is to incorporate the
bundle eCos package (
CYGPKG_BUNDLE) into your
This may be achieved directly using ecosconfig add on the command line, or the Build->Packages... menu item within the eCos Configuration Tool.
If the eCos zlib package CYGPKG_COMPRESS_ZLIB is configured then, when enabled, this option provides support for decompressing items. If the CYGPKG_COMPRESS_ZLIB package is not available, or this option is disabled, then only uncompressed items within a bundle can be read.
This option can be enabled to include support for the RFC 1321 MD5 Message-Digest Algorithm as a valid hash used to verify data integrity.
This option can be enabled to include support for the FIPS PUB 180-2 SHA-256 hash as a valid hash used to verify data integrity.
This option when enabled implements support for the standard IEEE 802.3 (Ethernet) CRC-32 as a valid hash used to verify data integrity.
This option defines the size of the internal buffer used for decompressing data. Currently it makes use of a dynamic memory allocation and so may need to be tuned appropriately for target systems with a small dynamic heap.
This option allows the host-side bundle tool to be automatically built on suitably capable systems.
Note: This option is disabled by default, since normally only a Linux system with a standard zlib library installation would automatically succeed. The package supplied host/Makefile provides an example of cross-building (under Linux) the host tool for Windows.
If this option is enabled then it provides access to individually controlled CDL debug options for various sub-systems or package features. This allows the detail and amount of debug information to be controlled. Normally such diagnostic output would only need to be enabled for developers working on the internals of the bundle processing.
This option enables the building of any bundle run-time verification tests included in the package.