Gem not working in 1.9.3 under Windows 7 64-bit about ashton HOT 9 CLOSED

Not a clue why it should be doing that. The rescue clause is not supposed to rescue in this situation - it just handles the different files that the compiler might generate.

I should just compile it myself really, before I upload it :$

from ashton.

So... what'll it take to get you to do that? :D I assume you already have a working version, so it just needs to be packaged into a gem, right? (I've never made a gem, so I don't know what'd be involved in altering the current one).

If I knew how to tell rubygems to show me the compiler output, I'd help you track it down. (I tried using --debug but it gives new meaning to the word "verbose" :P)

Actually, I'm going to try installing 64-bit versions of Ruby 2.0 and the DevKit and see if that works (the very few breaking changes from 1.9.x are a non-issue; I've just been too lazy to upgrade :$).

EDIT:

I just opened the gem file and it contains the bogus ashton.so (ELF) O_o

EDIT2:

Yay! I opened the gem in 7zip, deleted ashton.so, re-installed from the new .gem, and it made a working "PE-format" shared library!

from ashton.

How very odd...

from ashton.

I just had to do the fix again on 0.1.1... Sure would be cool if you could fix this for the next release. (No pressure! 😁)

from ashton.

I think you should be able to use "--version=ruby " when you install to force the source version and then it will compile locally (not a great solution, but saves editing the .gem file ;)).

I'll look into building a 2.x gem...though I need to find out what the convention is for building 32 and 64 bit versions...

from ashton.

Oops no, I mean "--platform=ruby"

from ashton.

Hmm, but Ashton is just a ruby source gem. I never got around to building a fat gem.

Poke me if I continue to forget to resolve this...

from ashton.

Duh. Yeah. Suddenly the penny dropped. Uploaded 0.1.3 to rubygems, which WILL be fine ;)

from ashton.

Works great! Thanks!

from ashton.