UK Ruby on Rails, Exalead, AWS, Consultancy - ImageScience and RubyInline on Windows Comments

Comment on 'ImageScience and RubyInline on Windows' by Rob

2008-02-18T20:04:56Z

I have now posted an updated version of these instructions here.
Rob

Comment on 'ImageScience and RubyInline on Windows' by Fabio

2008-02-15T00:38:26Z

Excelent job on the guides and on the win32 version of the gem, guys! :)

Comment on 'ImageScience and RubyInline on Windows' by Rob

2008-02-13T08:18:19Z

Hi Jim,

I used Sazima’s instructions last week to setup image_science and attachment_fu for a project I’m working on and it all worked first try: so yes if you follow Sazima’s instructions it should work for you!

Good luck, Rob

Comment on 'ImageScience and RubyInline on Windows' by Jim

2008-02-12T18:01:11Z

Hi guys!

I have found you after a long day trying to install imagescience on my windows for a ruby app. As you say I have felt as an acrobat and still something is wrong and I can not use the attachment_fu plugin because of that. Now I found you and I am going to try Sazima's way, is it correct? is it your final step-by-step guide?

Anyway thanks for the help

Jim

Comment on 'ImageScience and RubyInline on Windows' by Rob

2008-01-25T09:01:46Z

Thanks for that Sazima - I really need to update the article but haven't had chance yet.

It's amazing how much shorter the instructions are thanks to Luis’ work on the Win32 ImageScience gem - thanks again Luis!

Rob

Comment on 'ImageScience and RubyInline on Windows' by Sazima

2008-01-25T02:39:07Z

Hey Rob,

Just to summarize, I did the following and (apparently) it works:

attachment_fu
- Ruby Inline: gem install RubyInline
- ImageScience: gem install .\image_science-1.1.3-i386-mswin32.gem (http://mmediasys.com/ruby/)
- FreeImage (http://sf.net/projects/freeimage)
  - Copy FreeImage.dll from the dist directory to C:\Windows\system32.
  - Copy FreeImage.h from the dist directory to $RUBY_HOME\include (you might need to create this directory).
  - Copy FreeImage.lib from the dist directory to $RUBY_HOME\lib.

Cheers, Sazima

Comment on 'ImageScience and RubyInline on Windows' by Mark

2008-01-21T20:15:01Z

Awesome posting _ I got my XP system up and running in no time!

Comment on 'ImageScience and RubyInline on Windows' by Luis Lavena

2007-12-04T13:21:56Z

Yeah!, the OCI team need to hear us! ;-)

Eh, actually, I'm part of the team :-P

I'm working on it, but still need to have a stable environment before release something in the wild.

Keep one eye on ruby-talk for announcements :-D

Comment on 'ImageScience and RubyInline on Windows' by Rob

2007-12-04T08:47:32Z

That’s excellent news. I expect ImageScience will become a whole lot more popular on Windows now that the hassles of compilation have been removed.

Maybe now we should try and convince the one-click installer team to upgrade to a newer version of the C compiler!

Comment on 'ImageScience and RubyInline on Windows' by Luis Lavena

2007-12-03T14:56:51Z

Yeah, the ruby extensions experience on Windows remove all the joy of using Ruby (ala: it plain sucks).

Good a few minutes to spare and generated the proper gems with VC6:

http://mmediasys.com/ruby/

Ryan is still busy (with his project) but promised will integrate all the pending patches to Hoe, Inline and ImageScience soon.

Comment on 'ImageScience and RubyInline on Windows' by Rob

2007-12-02T21:16:23Z

Hi Luis,

Thanks for the warning - I do have an old copy of Visual C++ 6.0 so I'll have to dust off the CD and get it installed. I got the idea of using a newer version of the C compiler from this post (which it occurs to me that I didn't credit for the changes made to config.h).

I also came across this rant (which is quite funny too) about compiling Ruby extensions on Windows which might be useful background reading.

Thanks again, Rob

Comment on 'ImageScience and RubyInline on Windows' by Luis Lavena

2007-12-02T18:25:48Z

Rob, very instructive tutorial, but be careful.

The problem with compiling ruby extension with outher ompiling besides VC6 is that the extensions will link to a different runtime than the one ruby is linked to (MSVCR80.dll for the extension, MSVCRT.dll for ruby). Also, FreeImage.dll with another runtime (afaik, cannot check it right now).

This posses a huge problem: memory allocated by one runtime cannot be freed by another version of the runtime, and that can lead to huge and unknown crashes in your application.

I've submitted a few patches for Inline and Hoe to simplify the packaging of inlined libraries, but those are getting dusty on RubyForge since Ryan didn't take a look to them.

We should start doing lobby and bugging Ryan to accept them, so ParseTree and other inlined gems get good and proper windows support.

I already have provided with debugging support of Aman Gupta good ParseTree mswin32 gems compiled with VC6 (sequel guys use it).

ImageScience isn't so complex as ParseTree, but the proposed patches will make it simpler.

So: help me bugging Ryan and get those patches commited! :-D