[Vm-dev] Why the hell directives for compiling with clang were not taken into account

K K Subbu kksubbu.ml at gmail.com
Tue Apr 3 14:34:54 UTC 2018


On Tuesday 03 April 2018 06:00 PM, Eliot Miranda wrote:
> I'm feeling beaten down.  Perhaps you could read the code?  Compare 
> what's in platforms/unix/config with what's in 
> build.macos32x86/common build.macos64x64/common build.win32x86/common
> build.win64x64/common
> 
> And then think about the "necessary configure step".  To what extent 
> does it make sense to run a configure step on a build machine that 
> makes a binary that is downloaded and used on machines that may 
> differ markedly from that build machine?

The configure script in Autoconf accumulates lots of platform-fu (see
configure:5668) for all the UNIX/Linux variants and quirks.

Mac or Win ports have to deal only with a handful of variants, so
hand-crafted Makefiles are sufficient. But Unix/GNU/Linux ports are so
numerous and diverse that Ian Piumarta (?) brought in autoconf to ease
porting Squeak to all these variants.

If we don't intend to support all the 100+ variants of GNU/UNIX/Linux 
out there but only a handful, then manual makefiles are sufficient.

GNU Make is available on GNU/Linux/Mac/Win so we could create a single 
top level Makefile for all three platform builds and let the configure
handle other ports. CMake is another possibility but it requires meta 
makefiles to be created from scratch :-(.

Regards .. Subbu


More information about the Vm-dev mailing list