Re: sablevm + windows

Hi Chris (and others),
thanks for your reply. I have been following up on the items you 
mentioned, with the mailing list and archives in particular.

I was not able to check out Mélanie's sandbox in the way you suggested
($ svn co svn+ssh://svn.sablevm.org/public/developers/mlord 
sablevm-mlord)
probably because I don't have an ssh account. However I was able to 
fetch
svn.sablevm.org/developers/mlord/sandbox
which hopefully is the same (disabuse me of that notion if appropriate).

The porting document there was very helpful and for our use I've 
translated it into English. It's in the same format and not wiki-ized, 
but even so it may be useful to have on sablevm.org -- just let me know 
where.

It seems that many of the changes mentioned there have been made to 
subsequent versions of sablevm and classpath, so I should probably add 
a caveat to that effect.

I'm still having a problem getting a proper version of libffi built, 
and will attack that further tomorrow. Part of the problem is that I'm 
not very familiar with auto* tools (but learning rather quickly).

There is a libffi change to support darwin and I'm not sure if that has 
made it into the official gnu release. However it works well on Mac OS 
X (I'm a Mac developer from way back), and sablevm+classpath are 
running there nicely (OS X 10.3).

Regards.....Peter

On Oct 3, 2004, at 6:21 PM, Chris Pickett wrote:

> Peter Lovell wrote:
>> Hi all,
>> I see from the archives that there has been work done to build 
>> sablevm on windows (Cygwin). There is a problem with libffi being 
>> available only as s static library, whereas sablevm wants it to be 
>> shared, and someone mentioned that there was a solution.
>> But the post did not include the details of the 
>> solution/workaround/hack which made this possible.
>> I'd greatly appreciate it if someone could let me know what was done. 
>> And I'd also appreciate any suggestions on other items for a windows 
>> port. This will be my full-time task starting this week and I 
>> certainly don't need to re-do work done by others.
>
> Hi Peter,
>
> I'm sorry that no-one got back to you since your last message, we're 
> all rather busy.  Sometimes you can find one of us on #sablevm
>
> There are numerous threads about cygwin/mingw/native ports of sablevm. 
> Check sablevm-user and sablevm-developer, and check the bug-tracker.  
> If you want to make a detailed summary of what you read, including the 
> attempted/proposed/working solutions and the current status of all 
> three ports (the goal being that we don't have to keep rehashing the 
> same points nor ever troll through old posts again), and contribute it 
> to our wiki and file appropriate bugs or comments to bugs in the 
> bug-tracker, that would be well-received.
>
> You'll also want to check out Melanie Lord's sandbox using svn.
>
> $ svn co svn+ssh://svn.sablevm.org/public/developers/mlord 
> sablevm-mlord
>
> Cheers,
> Chris
>
> _______________________________________________
> SableVM-devel mailing list
> [email protected]
> http://sablevm.org/lists/control/listinfo/sablevm-devel
>