From: Luis Lavena <luislavena@...>
Date: 2008-10-05T00:23:32+09:00
Subject: Re: Making/Compiling Gems on Windows with MinGW

On Oct 3, 6:15 pm, Cayce Balara <ho...@balara.com> wrote:
> Whenever I try to install a gem that doesn't have a precompiled binary
> available I get an error like this:
>
> Provided configuration options:
>         --with-opt-dir
>         --without-opt-dir
>         --with-opt-include
>         --without-opt-include=${opt-dir}/include
>         --with-opt-lib
>         --without-opt-lib=${opt-dir}/lib
>         --with-make-prog
>         --srcdir=.
>         --curdir
>         --ruby=c:/server/ruby/bin/ruby
>
> This is coming out of the call to the extconf.rb for the gem. If I try
> to execute that directly, the options don't seem to change. For
> instance:
>
> ruby ext/extconf.rb --without-opt-include=c:/server/mingw/include
>
> I run that command and the error report shows the same, no change to the
> reported --without-opt-include configuration option.
>
> So it doesn't appear as if I'm calling it correctly since the custom
> configuration option is not making it through.
>
> More importantly, where are the default configuration options stored,
> and how can I change them to point to the MinGW files for make-ing and
> compiling?
>
> thanks.

What gem are you trying to compile?

Also, if you have gcc.exe and make.exe in your PATH, there will be no
issues with it.

Keep in mind that the ruby version you're using *must* be the one
build with MinGW, and will not work with the one build with VC6. To
spot this difference run "ruby -v" and see the platform information.

mswin32: VC6 build
mingw32: MinGW (GCC) build

using --without-* you're excluding the 'include' files, the opposite
that you want to achieve :-)

Use --with-opt-include=C:/server/mingw/include

HTH,
--
Luis Lavena