Previous definition caused issues when compiling natively since DevKit was not enabled at the proper time. This is caused by ports getting prepend into the dependency list of `compile` task way before than it should have been. This change, while feels like a hack, gets the job done. And I'm making a cup of tea to celebrate it
The included configuration aims to compile and test builds of sqlite3-ruby gem against a native Windows environment provided by AppVeyor platform. Add `devkit` task that prepends both compile and native ones and ensures RubyInstaller's DevKit is enabled in the PATH prior compilation.
Make 'sqlite3_native' compilation task available as constant so other tasks can lookup into definitions like `cross_compile` and configure options before triggering the build. This is of course a massive hack around ExtensionTask and Rake, but at this time there is no better alternative
--enable-static triggers Ruby's static compilation, not just ours.
- Relocated FAQ out of doc folder - Added manifest support - Renamed Changelog and README to suit better Hoe defaults. - Include extension in gem specification. - Advertise rake-compiler as development dependency. - Ensure extension is always compiled before tests. - Add test database to cleanup. - Bumped SQLite to 3.6.16
Rake-compiler cross compilation options only should be enabled when running on platforms like Darwin or Linux.
- Still to iron issues with i586-mingw32msvc-gcc and exported symbols from SQLite3 library.