On Mon, 2004-09-06 at 12:42, Dan Sugalski wrote:
> Right now configure.pl pulls a bunch of configuration information
> straight out of the current perl configuration. We need to stop that,
> and this is as good a time as any.
>
> If someone could go through and make a list of what info configure.pl
> pulls from perl, I'll start writing (or snagging :) the probing code
> to do it ourselves, so we can be perl-free, at least from a
> configuration standpoint.
I think right now that info is all in config/init/data.pl, and it's
actually fairly well documented. Here's all of the variables that rely
on the %Config data from Perl's Config.pm:
optimize => $optimize ? $Config{optimize} : '',
# Compiler -- used to turn .c files into object files.
# (Usually cc or cl, or something like that.)
cc => $Config{cc},
ccflags => $Config{ccflags},
ccwarn => exists($Config{ccwarn}) ? $Config{ccwarn} : '',
# Flags used to indicate this object file is to be compiled
# with position-independent code suitable for dynamic loading.
cc_shared => $Config{cccdlflags}, # e.g. -fpic for GNU cc.
# Linker, used to link object files (plus libraries) into
# an executable. It is usually $cc on Unix-ish systems.
# VMS and Win32 might use "Link".
# Perl5's Configure doesn't distinguish linking from loading, so
# make a reasonable guess at defaults.
link => $Config{cc},
linkflags => $Config{ldflags},
# ld: Tool used to build dynamically loadable libraries. Often
# $cc on Unix-ish systems, but apparently sometimes it's ld.
ld => $Config{ld},
ldflags => $Config{ldflags},
libs => $Config{libs},
exe => $Config{_exe}, # executable files extension
ld_shared => $Config{lddlflags},
ar => $Config{ar},
ranlib => $Config{ranlib},
make => $Config{make},
make_set_make => $Config{make_set_make},
--
Aaron Sherman <[EMAIL PROTECTED]>
Senior Systems Engineer and Toolsmith
"It's the sound of a satellite saying, 'get me down!'" -Shriekback
