At 06:49 PM 2/23/99 -0500, Bill Cattey wrote:
Information!
The Squeak 2.3 VM builds fine under: gcc version egcs-2.91.57 19980901 (egcs-1.1 release) but does not build correctly under gcc version 2.8.1
[snip]
There seems to be a great deal of difficulty in building the VM for various configurations. The UNIX applications I ported to DOS invariably had a readme (or config.txt?) file with a whole list of configurations supported, and asked anyone who built a new one to add to the list. Is there a similar approach to the VM build for Squeak available in one place?
I seem to remember seeing something about a learn or teach utility that helped to build the makefile or something. I think a lot of UNIX utilities are available in Windows equivalents. Anybody know what the utility was? -- Richard A. Harmon "The only good zombie is a dead zombie" harmonra@webname.com E. G. McCarthy
On Wed, Feb 24, 1999 at 09:05:11AM -0600, R. A. Harmon wrote:
I seem to remember seeing something about a learn or teach utility that helped to build the makefile or something. I think a lot of UNIX utilities are available in Windows equivalents. Anybody know what the utility was?
GNU autoconf/automake/libtool
This is used by many other Open Source (tm) projects (even Netscape).
autoconf generates these nice ./configure scripts that build Makefiles and test for many common Unix-compatiblility problems.
IMHO it would be good to convert the UnixSqueak to use autoconf. (and I volunteer to do it).
A good introduction is available at
http://www.cygnus.com/~ian/configure/
From the Webpage:
Goals -----
The GNU configure and build system has two main goals.
The first is to simplify the development of portable programs. The system permits the developer to concentrate on writing the program, simplifying many details of portability across Unix and even Windows systems, and permitting the developer to describe how to build the program using simple rules rather than complex Makefiles.
The second is to simplify the building of programs distributed as source code. All programs are built using a simple, standardized, two step process. The program builder need not install any special tools in order to build the program.
Tools -----
autoconf provides a general portability framework, based on testing the features of the host system at build time. automake a system for describing how to build a program, permitting the developer to write a simplified Makefile. libtool a standardized approach to building shared libraries.
Marcus Denker wrote:
GNU autoconf/automake/libtool
This is used by many other Open Source (tm) projects (even Netscape).
autoconf generates these nice ./configure scripts that build Makefiles and test for many common Unix-compatiblility problems.
IMHO it would be good to convert the UnixSqueak to use autoconf. (and I volunteer to do it).
Although a mighty task, that's a good idea, because:
1. The Unix makefiles are far too complicated for users who only want to build a VM on their platform. 2. For example, generating a headless VM with
$ ./configure --enable-headless
is easier than modifying the source code. 3. Since feature based cpp defines (e.g. HAS_FEATURE_XY) will replace OS specific defines (e.g. SUNOS_56) in the C source code it is likely that it will be more readable.
Regards,
Jörg
squeak-dev@lists.squeakfoundation.org
-
Joerg Brunsmann -
Marcus Denker -
R. A. Harmon