This Ada library contains various utility packages for building Ada applications. This includes:
- A logging framework close to Java log4j framework,
- Support for INI and property files,
- A serialization/deserialization framework for XML, JSON, CSV, Forms
- Ada beans framework,
- Encoding/decoding framework (Base16, Base32, Base64, SHA, HMAC-SHA, AES-256),
- A composing stream framework (raw, files, buffers, pipes, sockets, encryption, decryption, LZMA compression, LZMA decompression),
- Several concurrency tools (reference counters, counters, pools, fifos, arrays),
- Process creation and pipes,
- Support for loading shared libraries (on Windows or Unix),
- HTTP client library on top of CURL or AWS.
Ada Util also provides a small test utility library on top of Ahven or AUnit to help in writing unit tests. Ahven is the default testing framework as it provides better reports.
- Cleanup build environment to drop configure
- Improvement of Util.Files.Walk to scan and honor a root .gitignore from any child directory
- Feature #55: Support indentation when writing JSON streams
- Feature #56: Support for pseudo tty when launching a process
- Feature #57: Support for OpenBSD
- New package Util.Files.Walk to iterate over directory trees and honor .gitignore
- Add support for custom log formatter (allow to translate log messages, filter messages, ...)
- Feature #48: Change the log time from UTC to Local Time (configurable)
- Fix #49: Perf report generates incorrect XML title attributes
- Fix #50: 128Bit AES-CTR Encoding doesn't work (thanks Adam Jasinski)
- Fix #53: Executor does not always stop the worker tasks
- Used spdx-tool to use
SPDX-License-Identifierin headers
If you are using Alire in your project, run the following command within your Alire project to use the library:
alr with utilada
Depending on your project, you may need one or some of the following other components:
alr with utilada_aws
alr with utilada_curl
alr with utilada_lzma
alr with utilada_unit
alr with utilada_xml
If you don't have Alire or want to build and install the library
on a specific place, run a setup command to configure the build as well as installation
directory.
For a detailed description on how you can configure, build and install the library
refer to the Installation guide.
Otherwise, you can easily configure and build the library with the steps described below.
The support for AWS, Curl, LZMA and XML/Ada are enabled only when a HAVE_XXX=yes configuration
variable has defined. Run the setup command that records in the Makefile.conf the configuration
you want to build.
The HAVE_ALIRE configuration allows you to build with Alire or not.
The UTIL_OS configuration is mandatory for the setup to indicate the build host configuration.
It must one of the allowed values defined in utilada_conf.gpr GNAT project in the
Os_Version_Type declaration:
type Os_Version_Type is ("none", "unix", "windows",
"linux32", "linux64", "win32", "win64", "macos64",
"netbsd32", "netbsd64", "freebsd32", "freebsd64");
The example below enables the XML/Ada and AWS components but disables the Curl and LZMA support and disables the use of Alire to build the library.
make setup BUILD=debug PREFIX=/build/install \
UTIL_OS=linux64 \
HAVE_XML_ADA=yes HAVE_AWS=yes \
HAVE_CURL=no HAVE_LZMA=no HAVE_ALIRE=no
Then build, run the unit tests and install by using:
make
make test
make install
To use the installed libraries, make sure your ADA_PROJECT_PATH contains the directory
where you installed the libraries (configured by the PREFIX=<path> option in the setup phase).
The installed GNAT projects are the same as those used when using Alire.
The samples are built by using:
cd samples
alr build
or by running:
make samples