Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
351 lines (224 sloc) 9.91 KB
#!/usr/bin/perl -w
# 2.0
# $Id$
# Author: Brent Dax
use 5.005_02;
use strict;
use vars qw($parrot_version @parrot_version);
use lib 'lib';
use Parrot::BuildUtil;
use Parrot::Configure::RunSteps;
$parrot_version = parrot_version();
@parrot_version = parrot_version();
# Handle options
my %args;
for(@ARGV) {
my($key, $value)=/--(\w+)(?:=(.*))?/;
$value = 1 unless defined $value;
for($key) {
/version/ && do {
my $cvsid='$Id$';
print <<"END";
Parrot Version $parrot_version Configure 2.0
/help/ && do {
print <<"EOT";
$0 - Parrot Configure 2.0
--help Show this text
--version Show version information
Steps may take additional options of the form --name or --name=value.
Popular ones include:
--ask Have Configure ask for commonly-changed info
--nomanicheck Don't check the MANIFEST
--debugging Enable debugging
--cc=(compiler) Use the given compiler
--ld=(linker) Use the given linker
--intval=(type) Use the given type for INTVAL
--floatval=(type) Use the given type for FLOATVAL
print <<"END";
Parrot Version $parrot_version Configure 2.0
Copyright (C) 2001-2002 Yet Another Society
Hello, I'm Configure. My job is to poke and prod your system to figure out
how to build Parrot. The process is completely automated, unless you passed in
the `--ask' flag on the command line, in which case it'll prompt you for a few
pieces of info.
Since you're running this script, you obviously have Perl 5--I'll be pulling
some defaults from its configuration.
#Run the actual steps
print <<"END";
Okay, we're done!
You can now use `make' (or your platform's equivalent to `make') to build your
Parrot. After that, you can use `make test' to run the test suite.
Happy Hacking,
The Parrot Team
=head1 TITLE
parrotconfig - Parrot Configure
=head1 NOTE
This document is NOT about how to use Configure--it's about Configure's design. For
information on using Configure, type C<perl --help> (or your platform's
equivalent) at a command line prompt.
Configure is broken up into I<steps>. Each step contains several related I<prompts>,
I<probes>, or I<generations>. Steps should be mostly of a single type, though some overlap
is allowed (for example, allowing a probe to ask the user what to do in an exceptional
The directory F<config> contains subdirectories for each type of step. Each step should
consist of I<exactly one> .pl file and any number of supporting .c, .in, etc. files. Any
supporting files should be in a folder whose name is the same as the basename of the step's
.pl file; for example, if F<> uses F<>, F<> should be in a directory
called F<foo>; the full path might be F<config/auto/foo/>.
Generally, when adding a new test you should add a new step unless a test I<clearly> belongs
in a current step. For example, if we added a new user-configurable type called C<FOOVAL>,
you should add the test for its size in F<auto/>; however, if you were testing
what dynaloading capabilities are available, you should create a new step.
=head2 Initialization Steps
I<Initialization steps> are run before any other steps. They do tasks such as preparing
Configure's data structures and checking the MANIFEST. These will rarely be added; when
they are, it usually means that Configure is getting significant new capabilities.
They're kept in the directory F<config/init>.
Initialization steps usually do not output anything under normal circumstances.
=head2 Prompts
Prompts ask the user for some information. These should be used sparingly. A step
containing prompts is an I<interactive step>. Interactive steps should be in the
F<config/inter> folder.
Interactive steps often include simple probes to determine good guesses of what the user
will answer. See L</Prompt or Probe?> for more information.
Interactive steps virtually always output something.
=head2 Probes
Probes are automated tests of some feature of the computer. These should be used wherever a value
will not often need to be modified by the user. A step containing probes is an I<automatic step>.
Automatic steps should be in the F<config/auto> folder.
Automatic steps usually do not output anything under normal circumstances.
=head2 Generations
Generations create files needed after Configure has completed, such as Makefiles and configuration
headers. A step containing generations is a I<generation step>. Generation steps should be in the
F<config/gen> folder.
Generation steps usually do not output anything under normal circumstances.
=head2 Prompt or Probe?
It can sometimes be hard to decide whether a given step should be an automatic or an interactive
step. The guiding question is I<Would a user ever want to change this?>, or conversely, I<Is this
something that can be completely determined without user intervention?> A step figuring out what
the compiler's command is would probably be an interactive step; conversely, a step figuring out
if that command is connected to a specific compiler (like gcc) would be an automatic step.
=head2 Adding Steps
New steps should be added in one of the three folders mentioned above. They should include the
C<Parrot::Configure::Step> module, described below.
All steps are really modules; they should start with a declaration setting the current package
to C<Configure::Step>. They should define the following:
=over 4
=item C<$description>
A short descriptive message that should be printed before the step executes. Usually, interactive
steps have long, friendly descriptions and other steps have terse descriptions ending in "...".
Some example descriptions:
=over 4
=item F<inter/>
Okay, I'm going to start by asking you a couple questions about your
compiler and linker. Default values are in square brackets;
you can hit ENTER to accept them. If you don't understand a question,
the default will usually work--they've been intuited from your Perl 5
=item F<auto/>
Determining if your compiler supports computed goto...
=item F<gen/>
Generating a config.h header for Parrot...
Note that on non-interactive steps, the text C<"done."> will be printed after the description when the step
finishes executing; for example, the user will see:
Determining if your compiler supports computed goto...done.
=item C<@args>
This contains the names of any command-line arguments the step cares about. Command-line arguments
are standardized in Configure; this will be described later in more detail.
=item C<Configure::Step::runstep>
This is called to actually execute the step. The command-line arguments that your module said it
cared about are passed in; they come in the same order as in C<@args>, and any that weren't specified
are passed as C<undef>.
Configure won't execute your step by default unless it's specifically told to. To do this, edit the
C<Parrot::Configure::RunSteps> module's C<@steps> array. Steps are run in the sequence in which
they appear in C<@steps>.
A template for a new step might look like this:
package Configure::Step;
use strict;
use vars qw($description @args);
use Parrot::Configure::Step;
sub runstep {
=head2 Command-line Arguments
Command-line arguments look like C</--\w+(=.*)?/>; the equals sign separates the name and the value.
If the value is omitted, it's assumed to be 1. The options "--help" and "--version" are built in to
Configure; any others are defined by steps. "--help" lists some common options.
Steps use the C<@args> array to list any options they're interested in. They should be listed without
the dashes.
=head2 Building Up Configuration Data
The second step is F<config/init/>, which sets up a C<Configure::Data> package. You get and set
Configure's data by calling methods on this package. The methods are listed below.
=over 4
=item C<< Configure::Data->get(keys) >>
Returns the values for the given keys.
=item C<< Configure::Data->set(key, value, key, value, ...) >>
Sets the given keys to the given values.
=item C<< Configure::Data->keys() >>
Returns a list of all keys.
=item C<< Configure::Data->dump() >>
Returns a string that can be C<eval>ed by Perl to create a hash representing Configure's data.
=head2 C<Parrot::Configure::Step>
The C<Parrot::Configure::Step> module contains utility functions for steps to use. They include the following:
=over 4
=item C<prompt(message, default)>
Prints out "message [default] " and waits for the user's response. Returns the response, or the default if the
user just hit ENTER.
=item C<cc_gen(file)>
Calls C<genfile(file, 'test.c')>.
=item C<cc_build()>
Calls the compiler and linker on F<test.c>.
=item C<cc_run()>
Calls the F<test> (or F<test.exe>) executable.
=item C<cc_clean()>
Cleans up all files in the root folder that match the glob I<test.*>.
=item C<genfile(infile, outfile)>
Takes the given I<infile>, substitutes any sequences matching C</\$\{\w+\}/> for the given key's value in
Configure's data, and writes the results to I<outfile>.
=head2 Moved Files
Several files have been moved from their original locations to new ones.
=over 4
=item F<*/>
Moved to F<config/gen/makefiles> and renamed appropriately.
=item F<>
Moved to F<config/gen/config_h>.
=item F<>
moved to F<config/gen/config_pm>.
=item F<>
Deleted; F<lib/Parrot/> now doesn't need to be generated.
=item F<hints/*>
Moved to F<config/init/hints> and rewritten.
=item F<platforms/*>
Moved to F<config/gen/platform>.
=item F<test*.c>, F<test*>
Moved to various subdirectories of F<hints/auto>.
Something went wrong with that request. Please try again.