From: Roger Pack <rogerpack2005@...>
Date: 2010-07-15T23:19:23+09:00
Subject: Re: Ruby for Windows Mobile (Win CE, CeGCC)

Maxim Sokolovsky wrote:
> Hi,
> I'm spent countless time in searching working ruby port on Windows
> Mobile. I'm not a fan of this OS, but already have device with it and
> still want to try programming in ruby on it. Google kicked me to:
> 
> 1. Howto compile and binaries ruby 1.8.x with Microsoft Visual Embedded
> C++ ( http://uema2.s8.xrea.com/ruby-mswince/ ). This works fine, but
> first of all it has Windows Mobile restriction on relative paths (ex.
> requiring 'lib/some.rb" - fails) and in addition it is 1.8 - not 1.9.
> There is no chance to use it as full value port, especially with
> rubygems.
> 
> 2. Success story of compiling ruby 1.8 with CeGCC cross compile
> toolchain ( http://cegcc.sourceforge.net/ ). Here is the topic of John
> Snowdon aka smed: http://www.ruby-forum.com/topic/143475 .  He
> successfully compiled ruby 1.8 even with rubygems (!). But for my sorry
> I can't reproduce his success and his blog with binaries is down too (
> http://www.target-earth.net/gadgets/code/rubyce.html ). In addition it
> is 1.8 branch and it will be more likely to use 1.9.x :-P
> 
> So, i'm  trying to compile ruby 1.9.1 p429 with CeGCC 0.59.1 under
> Ubuntu 10.04. First trouble that I get - is that confuigure script can't
> verify setpgrp() while cross-compiling. I solve it by adding
> "ac_cv_func_setpgrp_void=yes" to args. Next trouble was that configure
> script cannot detect pthread_kill function in any header, so it suggest
> not to use native threads, but in 1.9.x native threads - are mandatory.
> Some search kick me to mail list with howto compile pthreads-win32 (
> http://sourceware.org/ml/pthreads-win32/ ) with mingw32ce (mingw32 part
> of cegcc). I reproduced his success and now i have .dll, .a and headers.
> First my question is - can I it ( library compiled with mingw32ce) in
> compiling with cegcc? I'm novice in cross compiling and it would be
> greate if someone can hint how do I use it in compilng: some extra
> environment variable, makefile edits or maybe i can add some args to
> configure script? I think i choose dirty incorrect way, trying to hack
> makefile and sources in order to bypass errors. I added

If it's a dll it "should" work.


> io.c:3369: warning: implicit declaration of function 'rb_w32_is_socket'

I think this means that somehow compilation doesn't realize you are on 
windows.
The rubyinstaller list might be helpful, as well.
http://rubyinstaller.org/

I think I remember wince being removed recently from 1.9 branch (no 
maintainer, little interest), so grabbing a build *before* that might 
work better.  But I don't remember exactly.
-- 
Posted via http://www.ruby-forum.com/.