Passing --with-X-dir to bundled extensions while building 1.8.0

I can’t seem to find a “good” way to do this.

What I would like to have is a way to specify them to the top-level
configure script. But ext/extmk.rb isn’t set up to be able to handle
extra switches. Since it load()s the ext/*/extconf.rb files directly,
there doesn’t seem to be any other way.

I can run the extconf.rb files by hand, but then of course the
extensions are installed to site_ruby.

Steve

I said:

What I would like to have is a way to specify them to the top-level
configure script.

And of course there is one, and it’s obvious. If I had just thought
to blindly try it instead of thinking about it first… If you say
–with-X-dir=something to configure, that goes into
CONFIG[“configure_args”], which mkmf looks at.

Steve

Hi,

···

In message “passing --with-X-dir to bundled extensions while building 1.8.0” on 03/08/12, Steven Lumos slumos@yahoo.com writes:

What I would like to have is a way to specify them to the top-level
configure script. But ext/extmk.rb isn’t set up to be able to handle
extra switches. Since it load()s the ext/*/extconf.rb files directly,
there doesn’t seem to be any other way.

Supply your --with-X options to the configure. Makefile passes
–with-* options to the extconf.rb in the ext directory.

						matz.