[WIN] Compiling / Extending ruby using Visual Studio IDE

[Friedrich Dominicus]

"Shashank Date" <sdate@everestkc.net> writes:

> Has anybody successfully compiled or extended Ruby on the Windows platform
> using Microsoft Visual Studio 6.0 IDE ?

I have, and was too succesfull with lcc-win32.

>
> I am having difficulty doing both and wanted some guidance especially in
> setting up the Project correctly.

I strongly suggest you check out how extconf.rb should be written. See
Programmng Ruby chapter 17. Let Ruby take the task of writing the
Makefile.

>
> I have successfully compiled and extended using the extconf.rb method so
> this is not very urgent ... but still it would be nice to get there.

Ah sorry you used that, so what is your problem with it? Check out the
generated Makefile and you'll see what you should include.

> After
> some trial and error, I was able to compile stand alone C programs, once
> Ruby was compiled at the command prompt. But I could not generate C DLLs.
> I'm pretty sure I am missing some critical step ... any help will be highly
> appreciated.

Hm, have you tried to build and use a simple DLL? IIRC there are some
Wizards there for that help.

Regards
Friedrich

[Simon Strandgaard]

On Sat, 28 Jun 2003 11:01:06 +0000, Shashank Date wrote:

> Has anybody successfully compiled or extended Ruby on the Windows platform
> using Microsoft Visual Studio 6.0 IDE ?
>
> I am having difficulty doing both and wanted some guidance especially in
> setting up the Project correctly.
>
> I have successfully compiled and extended using the extconf.rb method so
> this is not very urgent ... but still it would be nice to get there. After
> some trial and error, I was able to compile stand alone C programs, once

^^^^^^^^^^^
^^^^^^^^^^^

If I understand you correct, you are talking about 'embedding' ruby into
C. In order to understand eachother we must use same terminologi.
#1 'extensions' is when you compile some C code and use it within Ruby.
#2 'embedding' is when you interpret some Ruby code withing you C code.

From your earlier postings I would say that you are doing #2 :-)
Am I right ?

> Ruby was compiled at the command prompt. But I could not generate C DLLs.
> I'm pretty sure I am missing some critical step ... any help will be highly
> appreciated.

I know nothing about windows.. sorry I cannot help.


--
Simon Strandgaard

[Shashank Date]

"Simon Strandgaard" <0bz63fz3m1qt3001@sneakemail.com> wrote in message

> > some trial and error, I was able to compile stand alone C programs, once

> ^^^^^^^^^^^
> If I understand you correct, you are talking about 'embedding' ruby into
> C. In order to understand eachother we must use same terminologi.

Agreed 100 %.

> #1 'extensions' is when you compile some C code and use it within Ruby.

That is what I meant when I mentioned C-DLLs.

> #2 'embedding' is when you interpret some Ruby code within you C code.

And that is what I meant when I mentioned stand alone C programs.

> From your earlier postings I would say that you are doing #2 :-)
> Am I right ?

So I am trying to do both :-)
But yes, in my earlier postings you helped me do the embedding part.
Thanks a lot again.

>

> > Ruby was compiled at the command prompt. But I could not generate C

DLLs.

> I know nothing about windows.. sorry I cannot help.

Appreciate your time and attention, nevertheless.

> Simon Strandgaard

-- shanko

[Shashank Date]

"Friedrich Dominicus" <frido@q-software-solutions.com> wrote in message
[snip]

> ....so what is your problem with it?
> Check out the generated Makefile and you'll see what you should include.

^^^^^^^^^^^^^^^^^^^^^^^^^
I'm struggling with precisely this -- it will be just a matter time before I
figure it out.
Am being lazy that's all ;-). Wanted to see if someone has already invented
the wheel.