Tool for compiling tables of leapseconds, for use with libiso8601.
Go to file
Laurence Withers de1d803f6d Update for 2012-06-30 leap second 2012-01-07 17:42:15 +00:00
scripts Update build system 2012-01-07 17:39:43 +00:00
src Update for 2012-06-30 leap second 2012-01-07 17:42:15 +00:00
.gitignore Import skeleton 2009-01-03 22:59:27 +00:00
COPYING Import skeleton 2009-01-03 22:59:27 +00:00
README Update build system 2012-01-07 17:39:43 +00:00
config Update build system 2012-01-07 17:39:43 +00:00
make.sh Update build system 2012-01-07 17:39:43 +00:00
run-test.sh Update build system 2012-01-07 17:39:43 +00:00
version Update build system 2012-01-07 17:39:43 +00:00

README

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

leaptable-compiler
========================================================================
Copyright: ©20092012, Laurence Withers
Author: Laurence Withers <l@lwithers.me.uk>
License: GPLv3

See file COPYING for detail license information.

Really Quick Instructions
-------------------------

To build: ./make.sh
To install: ./make.sh install

You might want to edit 'config' first. You might also want to set
'INSTALL_PREFIX', which is prepended onto the destination of any
installed file.

Purpose
-------

This project contains a single executable, leaptable-compiler, which is
used to compile, dump or verify the contents of a table of leap seconds
in a format suitable for loading with libiso8601.

See http://www.lwithers.me.uk/usr/src/libiso8601/ for details.

Instructions
------------

Use --help for usage info.

In compile mode, it takes a text file (or stdin) with an ISO8601-format
date on each line. Each date corresponds to a day with a positive leap
second, e.g.:

	2005-06-30
	2005-12-31
	2008-12-31

This file is compiled into the binary format expected by libiso8601's
iso8601_leap_table_load() function.

In dump mode, the binary file is dumped into a text file. In verify
mode, the library is used to load a compiled file, and some basic tests
are performed to check the library behaviour matches what is expected.