Re: [ruby-fltk-devel] How to choose alternate C++ compiler?

[Jeremy H. <je...@ch...>]

On Thu, Apr 06, 2006 at 12:28:30AM -0500, Albert Chin wrote:

> ruby-fltk uses the same compiler used to build ruby. However, if
> fltk was built with a C++ compiler, ruby-fltk should use it in
> extconf.rb, especially if a non-GCC compiler was used. 

I'm not sure I understand.  Both FLTK and Ruby-FLTK are written in C++
so they are *always* built with a C++ compiler.  Ruby-FTLK uses a
hack: extconf.rb loads cxx.rb , which goes through the configuration
and replaces gcc for g++ .  Do you need something like this to happen
for non-gcc compilers too?

> How about addition an option, --with-cxx=<compiler> to use for the
> compile tests in extconf.rb? How would I do this?

I don't know, I'm not an extconf.rb hacker.  I've just looked through
mkmf.rb but I can't make much sense of it.  It seems to automatically
parse all arguments of the form --foo=bar, but I can't find an
argument that affects the value of cc_command .

On Unix FLTK installs a fltk-config script, so the ideal solution
there is to set the compiler to `fltk-config --cxx`.  I've no idea if
this would work on other platforms.  What OS are you running?

I'll take this to the FLTK mailing list and the Ruby newsgroup.
Hopefully they can turn up something useful.  I haven't had much luck
with Google so far.

Sorry I can't be more help at the moment.  I'll get back to you when I
find out more.

Cheers, 

Jeremy Henty