Ruby, Windows, and Matlab

S

SER

Hello Rubyvolk,

I'm having a frustrating time trying to get a basic Matlab binding
working for Ruby on Windows, and I'm hoping that somebody will have
some ideas for moving me forward on this.

First, a caveat: I loath Windows, and am expecting that most of my
troubles are due to the fact that some part of my brian required for
Windows to make sense to me is retarded.

What I'm attempting to do is compile a Matlab binding on Windows. The
binding works fine on *nix machines, but I keep encountering failures
when I try to get it compiled on Windows.

Matlab has its own make process (mbuild) which works with a few
compilers (cl and lcc). In the process of trying to get this working,
I've discovered that (a) the main pre-compiled Ruby distribution uses
cl, and (b) Ruby won't compile with lcc. (b) is especially depressing,
because Matlab likes lcc, and I can barely get cl to compile anything
at all. Ancillory is that it is either impossible or a royal pain in
the tuckus to force mkmf to use mbuild.

Before I go into any more details, then, I'd like to know if anybody
knows whether it is possible to get mkmf to use a different compiler
than whatever was used to compile Ruby. In other words, to compile
Ruby bindings, is it *required* to use the compiler that was used to
compile the Ruby interpreter?

--- SER
 
S

Shashank Date

hi,

In other words, to compile
Ruby bindings, is it *required* to use the compiler
that was used to compile the Ruby interpreter?

I believe the one-click installer was built using VC++
7.0 and if that is true then yes, to expect your
compiled Ruby bindings to work with the Ruby
interepreter you have to compile it using that
compiler. I know that Ruby compiled with VC++ 6.0 was
also compatible with MSYS+MingW but I am not sure how
far it is true now.

-- shanko



__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
 
S

Shashank Date

hi,

In other words, to compile
Ruby bindings, is it *required* to use the compiler
that was used to compile the Ruby interpreter?

I believe the one-click installer was built using VC++
7.0 and if that is true then yes, to expect your
compiled Ruby bindings to work with the Ruby
interepreter you have to compile it using that
compiler. I know that Ruby compiled with VC++ 6.0 was
also compatible with MSYS+MingW but I am not sure how
far it is true now.

-- shanko

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
 
M

Mohammad Khan

Depending of various severity levels Syslog have the following methods

debug
info
notice
warning
err
alert
emerg
crit


I am proposing to have an alias for the following methods,
err => error
emerg => emergency
crit => critical


Thanks
Mohammad
 
N

Nikolai Weibull

* Mohammad Khan said:
I am proposing to have an alias for the following methods,
err => error
emerg => emergency
crit => critical

I second that. Fine, that's what the log-levels may be called, but we
don't have to keep with a sad tradition of obfuscating the simple,
nikolai
 
C

Curt Hibbs

Shashank said:
hi,



I believe the one-click installer was built using VC++
7.0 and if that is true then yes, to expect your
compiled Ruby bindings to work with the Ruby
interepreter you have to compile it using that
compiler. I know that Ruby compiled with VC++ 6.0 was
also compatible with MSYS+MingW but I am not sure how
far it is true now.

The one-click installer was built with vc++ 7.1. Theoretically I MinGW build
is compatible, but I'm not sure how true that is in practice as there can be
subtle differences. For example, the FreeRIDE debugger works only when the
installer is compiled with vc++ 7.0 or 7.1. When its compiled with vc++ 6.0
the FreeRIDE debugger does not work. Don't know why???

Curt
 
K

Kaspar Schiess

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Curt Hibbs wrote:
| The one-click installer was built with vc++ 7.1. Theoretically I MinGW
build
| is compatible, but I'm not sure how true that is in practice as there
can be
| subtle differences. For example, the FreeRIDE debugger works only when the
| installer is compiled with vc++ 7.0 or 7.1. When its compiled with
vc++ 6.0
| the FreeRIDE debugger does not work. Don't know why???

Very often I find extconf.rb to fail early because of path/location
differences in compiler environments ( mingw to vc++ ). So a full ruby
build is needed for compiling extensions. Once that is done, full binary
compatibility with the vc++ 7.1 batteries included install very often
just happens right.

- --
kaspar

semantics & semiotics
code manufacture

www.tua.ch/ruby
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBZavZFifl4CA0ImQRAq0tAJ4sOGckjVaiCk1gZi27JCLM3xAriACgmlxd
7rYlBxsyOC6efRvYLb5N3AQ=
=Ufb/
-----END PGP SIGNATURE-----
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,997
Messages
2,570,239
Members
46,827
Latest member
DMUK_Beginner

Latest Threads

Top