|
From: Gene S. <gs...@ab...> - 2002-01-05 03:21:36
|
Claus Assmann wrote: > What about the software that uses state-threads? I would like to > use it (even though I haven't figured out the license issues) and > I would prefer if the entire system just "automagically" builds on > many OS. Hence I appreciate the efforts to use autoconf. However, > I agree that there should be no performance impact, i.e., runtime > decisions what to use. Maybe some "use these switches on this OS" > cases can be integrated? Currently that's done by hand by selecting > the correct OS target in the Makefile. I'm attaching a small patch to the 1.3c version which is supposed to facilitate building ST as a part of a larger software project. This patch allows to eliminate manual selection of target OS (if so desired). It doesn't affect current mechanism, it just adds new targets. CHANGES - 3 lines in Makefile. New targets have been added: "default", "default-debug", and "default-optimized" (same as "default"). Also, a symlink to the output directory is created at build time. That allows to use the library and header file without knowing the output directory name (which is OS-dependent) in advance. - New small script "osguess.sh" to automatically guess target OS. This script requires the "config.guess" utility (a part of GNU Autoconf) to do actual system info guessing. "config.guess" itself is not included with ST. You can use one from a larger "main" software project (if it uses Autoconf) or just use any config.guess available on your system. You can also get it directly from GNU: ftp://ftp.gnu.org/gnu/autoconf/ (same approach as with any other GNU tools). USAGE Specify path to the "config.guess" utility -- set the CONFIG_GUESS_PATH variable either by editing "osguess.sh" or via environment. Use "default" as a make target (make default). Hope it solves some of the problems. |