[chef] Re: Re: RE: Chef workstation on Windows

[Benjamin Bytheway < >]

We're trying to get chef client omnibus 11.4.4 currently.

I've tried using the windows ruby installer + devkit and install chef from gems. Installing win32-api from gems (--platform ruby to force a complie) appears to work, but when you try to require it, ruby can't find it. 

I did a manual install of the win32-api lib to site_ruby (not a gem) and it looks like ruby can find it that way, and knife runs (and MUCH faster).

I'll have to keep digging and see why win32-api gem doesn't install properly under 2.0.

On Wed, May 15, 2013 at 10:27 AM, Daniel DeLeo < " target="_blank"> > wrote:

I understand that Ruby 2.0 has some huge fixes that make the gem loading faster, but it looks like chef + ruby2 on Windows isn't working yet (win32-api gem isn't working). Is there a roadmap anywhere to get to Ruby 2 support (especially on Windows)?

Many gems with C extensions pre-compile them on windows. Newish versions of ruby gems will show you this by default:

    $ gem list win32-api -r

    win32-api (1.4.8 ruby x86-mingw32, 1.4.6 x86-mswin32-60, 1.4.0 x86-mswin32-80, 1.0.4 mswin32)

If you `gem fetch win32-api --platform x86-mingw32` and then `gem unpack` it, you can see that there's ruby ABI (binary interface) specific paths:

    $ ls -1 lib/win32

    api.rb

    ruby18

    ruby19

So, basically you need to track down the gem owners (see http://rubygems.org/gems/win32-api ) and convince them to make a new release with ruby 2.0 ABI extensions.

In the meantime, if you have compilers on your system, you can install these gems manually with `gem install GEMNAME --platform ruby` which will pull the gem that just has the C source and build the extensions on your box. If you go this route, I'd appreciate if you can let us know how it all works.

Thanks in advance,

Ben Bytheway

Thanks,

-- 

Daniel DeLeo