On 10/19/07, Daniel Berger <[EMAIL PROTECTED]> wrote: > Hi all, > > Ok, I've lost track. What's the "proper" way to distribute separate gems > for MS Windows (or any platform really) where one is for users who want > to build from source vs those who just want a prebuilt binary? > > I'm curious because for the win32-api library I have two gems - one > that's source only (win32-api-1.0.3.gem), the other is a prebundled > binary (win32-api-1.0.3-mswin32.gem). With the latest beta when I do > "gem install win32-api" it never gives me a choice - it just grabs the > binary gem. > > Any ideas and/or suggestions? >
The idea is that binary gems for the #local or 'current' platform have higher priority over the ones with ::RUBY as platform. In case gem didn't find one for the specific local platform, will try to install the ruby one, which will trigger then the native extension build. To avoid the auto detection, eg, on windows: gem install mongrel --platform ruby Will fire the compile procedure. I'm currently testing a few gems that have native extensions and changing their gemspec/Rakefiles to the new platform (::CURRENT) to test them. So far, everything worked as expected (which is good) :-) The only thing that failed is using --source with a file:// URL ... URI cannot parse the drive letter and path correctly, but can live with that ;-) Regards everybody. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
