Re: Configure-generated files to seperate directories?

[Glynn Clements]

usenet@darrenhiebert.com (Darren Hiebert) writes:

> As far as I can tell, configure-generated files (i.e. files generated
> from .in files) are placed into the same directory as the .in files
> from which they are generated. Is there a means of making configure
> generate its files into a different directory that their corresponding
> .in files (e.g. subdirectories)?
>
> The reason I ask is that I want to be able to configure a single
> source tree such that it can be used to develop and build code for two
> different architectures simulataneously (i.e. without having to remove
> the previously compiled code and reconfigure). I want to be able to
> compile and test a single source tree for two architectures
> concurrently.

Configure reads the .in files relative to the directory in which the
configure script resides, but it writes the generated files relative
to the current directory.

For out-of-place builds, you need to cd to the build directory then
run configure using a path, e.g.

    mkdir build
    cd build
    ../configure

If for some reason the configure script can't locate itself, you can
the use --srcdir switch to specify the source directory explicitly.

-- 
Glynn Clements <glynn.clements@virgin.net>