About to take an airplane, going back to Argentina. Spent the last 2 weeks working hard on cool projects, meeting great people and hanging out with other Ruby developers.
Now to our business, rake-compiler
While Ruby Installer plans to move away from VC6, the need to standardize the building process of gems come up again, and again, and again.
Since the job of the Ruby Installer team is build the Installer, not fix all the worlds gems (we are not Superman, not even close), I decided is time to publish my approach to the problem.
Developers running OSX or Linux always had the option to cross compilation, but that is voodoo for Ruby developers, wonder why…
Anyhow, the purpose of rake-compiler is unify and reduce the glitches and the burden of building gems for Windows, where several compilers could can co-exist without killing each other.
Rake-compiler is not only for building gems for Windows, but also add some standardization and reduce the cryptic Rakefiles I have seen in the last couple of years.
As proof of concept, I’ll work tonight on sqlite3-ruby, giving some love to it and make it more easy to anyone.
You will be able to see the result in my fork tomorrow.
Oh, and you can check the github repository of rake-compiler here and fork it if you find something missing1
Bye!
1 A hint: Rake::JavaJarTask will be awesome to have 