Rubyinstaller devel - May 2009 - Updated MySQL and SQLite3 gems for Mingw

Hi All,


I''ve switched both of my Windows (XP and Vista) machines over to the
new mingw32 Ruby, and have so far had no problems!

I built the lastest MySQL and SQLite3 gems for my own use, and thought
I might share with others:

http://www.mikehodgson.com/gems/

I''ve got the process down to a fine art, so if anyone out there has
any requests, I''m all ears!


Mike

On Sat, May 16, 2009 at 7:45 PM, Mike Hodgson <mhodgson at gmail.com>
wrote:
> Hi All,
>
Hello Mike
> I''ve switched both of my Windows (XP and Vista) machines over to
the
> new mingw32 Ruby, and have so far had no problems!
>
Awesome to hear! I use it on a daily basis without issues, which means
is going to be more easy the migration now that assimilation (err,
adoption) has started!
> I built the lastest MySQL and SQLite3 gems for my own use, and thought
> I might share with others:
>
> http://www.mikehodgson.com/gems/
>
> I''ve got the process down to a fine art, so if anyone out there
has
> any requests, I''m all ears!
>
Did you based those in mysql-gem[1] and sqlite3-ruby[2] fork I have at github?

MySQL 5.1 is incompatible with the gem, lot of segfaults that I can
blame the extension itself (since DataMapper guys don''t face those).

The one in sqlite3-ruby is based on Jamis work and uses rake-compiler.

Can you share the steps you used to build those? I would really love
to integrate and get the smoother experience for everybody!

Cheers!

[1] http://github.com/luislavena/mysql-gem
[2] http://github.com/luislavena/sqlite3-ruby

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

Hi Luis,

I didn''t use your forks, I built from the original gem source. I
installed Mingw Ruby and the development environment and added the bin
directory to my path. Next, I copied the MySQL and SQLite development
files (headers and DLLs) into C:\ruby\devkit\msys\1.0.11\usr\local .
After that, it only required the usual change to the .gemspec (change
platform to Gem::Platform::CURRENT).

The MySQL gem is built on 5.0, I already ran into the 5.1 headaches :)

I was also able to build and install the do_mysql and do_sqlite3
extensions by just adding ''--with-mysql-dir=/usr/local/mysql''
and
''--with-sqlite3-dir=/usr/local/sqlite3''  to my gem install
lines. The
Data Objects extensions were always a pain on the VC6 OCI, so this was
nice :)

I''ll take a look at your forks now, I''ve been so busy at work
I
haven''t had time to keep up on new developments or look at
rake-compiler yet.

Mike


On Sat, May 16, 2009 at 6:51 PM, Luis Lavena <luislavena at gmail.com>
wrote:
>> I built the lastest MySQL and SQLite3 gems for my own use, and thought
>> I might share with others:
>>
>> http://www.mikehodgson.com/gems/
>>
>> I''ve got the process down to a fine art, so if anyone out
there has
>> any requests, I''m all ears!
>>
>
> Did you based those in mysql-gem[1] and sqlite3-ruby[2] fork I have at
github?
>
> MySQL 5.1 is incompatible with the gem, lot of segfaults that I can
> blame the extension itself (since DataMapper guys don''t face
those).
>
> The one in sqlite3-ruby is based on Jamis work and uses rake-compiler.
>
> Can you share the steps you used to build those? I would really love
> to integrate and get the smoother experience for everybody!

> The MySQL gem is built on 5.0, I already ran into the 5.1 headaches :)
Anybody know if the gem, built under linux + 5.1, works?
-=r

On Mon, May 18, 2009 at 10:08 AM, Roger Pack <rogerdpack at gmail.com>
wrote:
>> The MySQL gem is built on 5.0, I already ran into the 5.1 headaches :)
>
> Anybody know if the gem, built under linux + 5.1, works?
For linux? I think not, since the segfault is not Windows related but
bad pointer usage.

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

> For linux? I think not, since the segfault is not Windows related but
> bad pointer usage.
interesting.
-=r

On Mon, May 18, 2009 at 10:44 AM, Roger Pack <rogerdpack at gmail.com>
wrote:
>> For linux? I think not, since the segfault is not Windows related but
>> bad pointer usage.
>
> interesting.
But be my guest and check yourself and let us know :-)

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry