From 8162b471a7837d7e29ab2ab7588cfa9100d150e1 Mon Sep 17 00:00:00 2001 From: Christian Thaeter Date: Tue, 30 Jan 2007 20:14:10 +0100 Subject: [PATCH] autotoolified --- AUTHORS | 6 ++ ChangeLog | 195 ++++++++++++++++++++++++++++++++++++++++++++++++ INSTALL | 236 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Makefile | 14 ---- Makefile.am | 28 +++++++ NEWS | 6 ++ configure.ac | 29 ++++++++ 7 files changed, 500 insertions(+), 14 deletions(-) create mode 100644 AUTHORS create mode 100644 ChangeLog create mode 100644 INSTALL delete mode 100644 Makefile create mode 100644 Makefile.am create mode 100644 NEWS create mode 100644 configure.ac diff --git a/AUTHORS b/AUTHORS new file mode 100644 index 0000000..e76e88d --- /dev/null +++ b/AUTHORS @@ -0,0 +1,6 @@ +Design, first implementation: + + * Christian Thaeter + +NoBug/Authors (last edited 2007-01-30 19:02:58 by ct) + diff --git a/ChangeLog b/ChangeLog new file mode 100644 index 0000000..7035b02 --- /dev/null +++ b/ChangeLog @@ -0,0 +1,195 @@ +Tue Jan 30 06:14:54 2007 +0100 + + better logging control with NOBUG_LOG, set limits per flag + +Sat Jan 27 08:06:55 2007 +0100 + + Doc enhancement: BestPractices. wiki doc got completely reorganized, luckily that isnt seen here. + +Sat Jan 27 06:33:30 2007 +0100 + + retain old limit in nobug_env_get_flag when initializing flags + +Fri Jan 26 02:50:30 2007 +0100 + + little more precise definition of NOBUG_ON + +Fri Jan 26 02:46:18 2007 +0100 + + dump fixes + +Thu Jan 25 17:51:33 2007 +0100 + + little more precise definition of NOBUG_ON + +Wed Jan 24 13:53:14 2007 +0100 + + documentation update + +Wed Jan 24 13:46:27 2007 +0100 + + fixes Bugs/LimitIgnored + +Tue Jan 16 16:19:40 2007 +0100 + + merged limit and flag checking + +Sat Jan 13 22:44:44 2007 +0100 + + new LIMIT definition (prelimary) + +Fri Jan 12 20:48:11 2007 +0100 + + made fmt parameter optional for logging part2 + +Fri Jan 12 20:23:42 2007 +0100 + + made fmt parameter optional for logging + +Fri Jan 12 19:29:14 2007 +0100 + + TRACE alias for DEBUG + +Fri Jan 12 09:24:42 2007 +0100 + + control NOBUG_LIMIT with a env var + +Thu Jan 11 18:38:52 2007 +0100 + + doc update + +Thu Jan 11 18:38:32 2007 +0100 + + test fixes + +Thu Jan 11 18:37:35 2007 +0100 + + new _IF forms for assertions and logging + +Thu Jan 11 17:56:12 2007 +0100 + + small comment & whitespace changes only + +Sun Dec 24 05:30:43 2006 +0100 + + tweak gcc branch prediction + +Sun Dec 24 04:50:04 2006 +0100 + + more regular colong formatting in log output + +Sat Dec 23 16:12:37 2006 +0100 + + doc improvement + +Sat Dec 23 15:40:25 2006 +0100 + + w3m is much better than lynx + +Sat Dec 23 15:36:35 2006 +0100 + + new Makefile target to fetch README from wiki Doc + +Sat Dec 23 05:52:38 2006 +0100 + + MODE_CASE to MODE_SWITCH, _DBG macros only in alpha builds, BLOCK macro, disabled unfinished gdb support + +Fri Dec 22 16:58:34 2006 +0100 + + MODE_CASE and PASS, making some statements more sane + +Fri Dec 22 05:08:38 2006 +0100 + + ONCE macro for BUG, TODO, PLANNED + +Wed Dec 20 23:04:34 2006 +0100 + + forgotten to include stdlib.h + +Wed Dec 20 21:31:37 2006 +0100 + + make -DEBUG_ALPHA, -DEBUG_BETA or -DNDEBUG mandatory + +Wed Dec 20 01:48:59 2006 +0100 + + add __func__ to logging output + +Tue Dec 19 22:14:35 2006 +0100 + + double definition typo fix (LOGIF) + +Tue Dec 19 17:30:22 2006 +0100 + + removed NOBUG_NAMESPACE in favor of new flag based logging + +Tue Dec 19 03:38:45 2006 +0100 + + test rename and fixup + +Tue Dec 19 03:28:19 2006 +0100 + + corrections/macros renames + +Mon Dec 18 23:41:50 2006 +0100 + + DUMP and INVARIANT macro rename + +Mon Dec 18 23:05:40 2006 +0100 + + test update + +Mon Dec 18 21:50:27 2006 +0100 + + new logging features + +Mon Dec 18 19:58:26 2006 +0100 + + new logging capabilities + +Mon Dec 18 19:56:20 2006 +0100 + + doc new logging capabilities + +Sun Dec 17 23:49:36 2006 +0100 + + new FLAG macros for upcoming logging control + +Fri Dec 1 08:21:53 2006 +0100 + + NOTREACHED macro + +Wed Nov 29 04:21:00 2006 +0100 + + changed logging output from NOBUG to DEBUG, minor formatting changes + +Wed Nov 8 11:45:49 2006 +0100 + + include "NOBUG:" in LOG output + +Wed Nov 8 10:47:39 2006 +0100 + + NDEBUG incompatible with -DEBUG_{ALPHA|BETA} #error + +Tue Nov 7 06:29:11 2006 +0100 + + better assert + +Tue Nov 7 05:07:58 2006 +0100 + + legal stuff and simple makefile + +Tue Nov 7 04:36:03 2006 +0100 + + directory cleanup + +Mon Nov 6 19:54:58 2006 +0100 + + typo fix + +Mon Nov 6 19:46:03 2006 +0100 + + first real working revision + +Thu Oct 5 16:13:41 2006 +0200 + + Initial commit diff --git a/INSTALL b/INSTALL new file mode 100644 index 0000000..23e5f25 --- /dev/null +++ b/INSTALL @@ -0,0 +1,236 @@ +Installation Instructions +************************* + +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free +Software Foundation, Inc. + +This file is free documentation; the Free Software Foundation gives +unlimited permission to copy, distribute and modify it. + +Basic Installation +================== + +These are generic installation instructions. + + The `configure' shell script attempts to guess correct values for +various system-dependent variables used during compilation. It uses +those values to create a `Makefile' in each directory of the package. +It may also create one or more `.h' files containing system-dependent +definitions. Finally, it creates a shell script `config.status' that +you can run in the future to recreate the current configuration, and a +file `config.log' containing compiler output (useful mainly for +debugging `configure'). + + It can also use an optional file (typically called `config.cache' +and enabled with `--cache-file=config.cache' or simply `-C') that saves +the results of its tests to speed up reconfiguring. (Caching is +disabled by default to prevent problems with accidental use of stale +cache files.) + + If you need to do unusual things to compile the package, please try +to figure out how `configure' could check whether to do them, and mail +diffs or instructions to the address given in the `README' so they can +be considered for the next release. If you are using the cache, and at +some point `config.cache' contains results you don't want to keep, you +may remove or edit it. + + The file `configure.ac' (or `configure.in') is used to create +`configure' by a program called `autoconf'. You only need +`configure.ac' if you want to change it or regenerate `configure' using +a newer version of `autoconf'. + +The simplest way to compile this package is: + + 1. `cd' to the directory containing the package's source code and type + `./configure' to configure the package for your system. If you're + using `csh' on an old version of System V, you might need to type + `sh ./configure' instead to prevent `csh' from trying to execute + `configure' itself. + + Running `configure' takes awhile. While running, it prints some + messages telling which features it is checking for. + + 2. Type `make' to compile the package. + + 3. Optionally, type `make check' to run any self-tests that come with + the package. + + 4. Type `make install' to install the programs and any data files and + documentation. + + 5. You can remove the program binaries and object files from the + source code directory by typing `make clean'. To also remove the + files that `configure' created (so you can compile the package for + a different kind of computer), type `make distclean'. There is + also a `make maintainer-clean' target, but that is intended mainly + for the package's developers. If you use it, you may have to get + all sorts of other programs in order to regenerate files that came + with the distribution. + +Compilers and Options +===================== + +Some systems require unusual options for compilation or linking that the +`configure' script does not know about. Run `./configure --help' for +details on some of the pertinent environment variables. + + You can give `configure' initial values for configuration parameters +by setting variables in the command line or in the environment. Here +is an example: + + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix + + *Note Defining Variables::, for more details. + +Compiling For Multiple Architectures +==================================== + +You can compile the package for more than one kind of computer at the +same time, by placing the object files for each architecture in their +own directory. To do this, you must use a version of `make' that +supports the `VPATH' variable, such as GNU `make'. `cd' to the +directory where you want the object files and executables to go and run +the `configure' script. `configure' automatically checks for the +source code in the directory that `configure' is in and in `..'. + + If you have to use a `make' that does not support the `VPATH' +variable, you have to compile the package for one architecture at a +time in the source code directory. After you have installed the +package for one architecture, use `make distclean' before reconfiguring +for another architecture. + +Installation Names +================== + +By default, `make install' installs the package's commands under +`/usr/local/bin', include files under `/usr/local/include', etc. You +can specify an installation prefix other than `/usr/local' by giving +`configure' the option `--prefix=PREFIX'. + + You can specify separate installation prefixes for +architecture-specific files and architecture-independent files. If you +pass the option `--exec-prefix=PREFIX' to `configure', the package uses +PREFIX as the prefix for installing programs and libraries. +Documentation and other data files still use the regular prefix. + + In addition, if you use an unusual directory layout you can give +options like `--bindir=DIR' to specify different values for particular +kinds of files. Run `configure --help' for a list of the directories +you can set and what kinds of files go in them. + + If the package supports it, you can cause programs to be installed +with an extra prefix or suffix on their names by giving `configure' the +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. + +Optional Features +================= + +Some packages pay attention to `--enable-FEATURE' options to +`configure', where FEATURE indicates an optional part of the package. +They may also pay attention to `--with-PACKAGE' options, where PACKAGE +is something like `gnu-as' or `x' (for the X Window System). The +`README' should mention any `--enable-' and `--with-' options that the +package recognizes. + + For packages that use the X Window System, `configure' can usually +find the X include and library files automatically, but if it doesn't, +you can use the `configure' options `--x-includes=DIR' and +`--x-libraries=DIR' to specify their locations. + +Specifying the System Type +========================== + +There may be some features `configure' cannot figure out automatically, +but needs to determine by the type of machine the package will run on. +Usually, assuming the package is built to be run on the _same_ +architectures, `configure' can figure that out, but if it prints a +message saying it cannot guess the machine type, give it the +`--build=TYPE' option. TYPE can either be a short name for the system +type, such as `sun4', or a canonical name which has the form: + + CPU-COMPANY-SYSTEM + +where SYSTEM can have one of these forms: + + OS KERNEL-OS + + See the file `config.sub' for the possible values of each field. If +`config.sub' isn't included in this package, then this package doesn't +need to know the machine type. + + If you are _building_ compiler tools for cross-compiling, you should +use the option `--target=TYPE' to select the type of system they will +produce code for. + + If you want to _use_ a cross compiler, that generates code for a +platform different from the build platform, you should specify the +"host" platform (i.e., that on which the generated programs will +eventually be run) with `--host=TYPE'. + +Sharing Defaults +================ + +If you want to set default values for `configure' scripts to share, you +can create a site shell script called `config.site' that gives default +values for variables like `CC', `cache_file', and `prefix'. +`configure' looks for `PREFIX/share/config.site' if it exists, then +`PREFIX/etc/config.site' if it exists. Or, you can set the +`CONFIG_SITE' environment variable to the location of the site script. +A warning: not all `configure' scripts look for a site script. + +Defining Variables +================== + +Variables not defined in a site shell script can be set in the +environment passed to `configure'. However, some packages may run +configure again during the build, and the customized values of these +variables may be lost. In order to avoid this problem, you should set +them in the `configure' command line, using `VAR=value'. For example: + + ./configure CC=/usr/local2/bin/gcc + +causes the specified `gcc' to be used as the C compiler (unless it is +overridden in the site shell script). Here is a another example: + + /bin/bash ./configure CONFIG_SHELL=/bin/bash + +Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent +configuration-related scripts to be executed by `/bin/bash'. + +`configure' Invocation +====================== + +`configure' recognizes the following options to control how it operates. + +`--help' +`-h' + Print a summary of the options to `configure', and exit. + +`--version' +`-V' + Print the version of Autoconf used to generate the `configure' + script, and exit. + +`--cache-file=FILE' + Enable the cache: use and save the results of the tests in FILE, + traditionally `config.cache'. FILE defaults to `/dev/null' to + disable caching. + +`--config-cache' +`-C' + Alias for `--cache-file=config.cache'. + +`--quiet' +`--silent' +`-q' + Do not print messages saying which checks are being made. To + suppress all normal output, redirect it to `/dev/null' (any error + messages will still be shown). + +`--srcdir=DIR' + Look for the package's source code in directory DIR. Usually + `configure' can determine that directory automatically. + +`configure' also accepts some other, not widely useful, options. Run +`configure --help' for more details. + diff --git a/Makefile b/Makefile deleted file mode 100644 index 3f4d069..0000000 --- a/Makefile +++ /dev/null @@ -1,14 +0,0 @@ -prefix ?= /usr/local - - -all: - @echo "just 'make install' to install this header" - @echo "a optional 'prefix=/install_hierachy' is acknowledged" - -install: - mkdir -p $(prefix)/include - cp nobug.h $(prefix)/include/ - -doc: - w3m -no-cookie -dump 'http://www.pipapo.org/pipawiki/NoBug/Documentation?action=print' |\ - (read; read; cat) > README diff --git a/Makefile.am b/Makefile.am new file mode 100644 index 0000000..fdcd95f --- /dev/null +++ b/Makefile.am @@ -0,0 +1,28 @@ +# This file is part of the NoBug debugging library. +# +# Copyright (C) 2007, Christian Thaeter +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License version 2 as +# published by the Free Software Foundation. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program; if not, contact me. + +include_HEADERS = nobug.h + +meta: changelog + w3m -no-cookie -dump 'http://www.pipapo.org/pipawiki/NoBug/Documentation?action=print' |\ + (read; read; cat) > README + w3m -no-cookie -dump 'http://www.pipapo.org/pipawiki/NoBug/Authors?action=print' |\ + (read; read; cat) > AUTHORS + w3m -no-cookie -dump 'http://www.pipapo.org/pipawiki/NoBug/News?action=print' |\ + (read; read; cat) > NEWS + +changelog: + git log --no-merges | sed -e '/^\(commit\|Author:\).*/d;s/^Date: *//' >ChangeLog diff --git a/NEWS b/NEWS new file mode 100644 index 0000000..1068a0a --- /dev/null +++ b/NEWS @@ -0,0 +1,6 @@ +Transition to gnu autotools is in progress + + * -- ct 2007-01-30 18:45:19 + +NoBug/News (last edited 2007-01-30 18:46:00 by ct) + diff --git a/configure.ac b/configure.ac new file mode 100644 index 0000000..69e916a --- /dev/null +++ b/configure.ac @@ -0,0 +1,29 @@ +AC_INIT(nobug, 0.1) +AC_CONFIG_SRCDIR(nobug.h) +AC_CONFIG_AUX_DIR(scripts) +dnl AC_CONFIG_MACRO_DIR(m4) +AM_INIT_AUTOMAKE +AC_PREREQ(2.59) + +AC_COPYRIGHT([ +Copyright (C) 2007, Christian Thaeter + +This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License version 2 as +published by the Free Software Foundation. + +This program is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with this program; if not, contact me. +]) + + +AC_PROG_CC +AC_STDC_HEADERS + +AC_CONFIG_FILES(Makefile) +AC_OUTPUT -- 2.11.4.GIT