I absolutely had no problems with Ruby 2.0 and SQLite as a result of compiling SQLITE.h
Decision
Go to the following URL so that this problem is rejected by someone who has taken the next step in assembling the gem over the precompiled gemstones for other Rails 4 Rubyists who want to use Windows: this link .
Using a command like -with-opt-dir=<Path of Sqlite.3 bin, lib, include, and share folders>
. The only difficult part was the files that the sqlite3 official site provides, precompiled, which can be very difficult to consider a problem.
I can give you further instructions if you still have problems performing such actions using Ruby 2.0 and Rails 4.0.0.0beta1.
Using Ruby 2.0 with Windows should now be fine for you with respect to Sqlite3 and Rails. Pay attention to avoid using 64-bit Ruby 2.0 when it comes to Rails 4.0.0beta1, because one of the dependent stones for Rails 4 incorrectly indicates that your computer’s processor is incompatible with its gem requirements; it will be resolved soon.
Edit: Noticed that I was not as useful as I should have more explicit instructions; We have provided you with a link to those who have already managed to do this, and the files needed to run and run.
@Brian Petro: Actually, solving this problem is easy if you know how Gems and .h files at the end of the day sometimes work with construction. The problem is how some gems are processed using Ruby 2.0; starting with Ruby 2.0, precompiled gems that were convenient for previous versions of Ruby will not work if they have ABI Breakage; Sqlite3 gem is one of them:
source share