harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Morozova, Nadezhda" <nadezhda.moroz...@intel.com>
Subject RE: Harmony on Macosx [was Re: [jira] Created: (HARMONY-2374) [classlib][awt] Missing java2d code for OpenGL pipeline.]
Date Fri, 01 Dec 2006 15:05:48 GMT
>do we have any documentation about "porting to other system"? I think
>would be immensely helpful.

AFAIK, the only OS-specific info we have are:
- http://harmony.apache.org/roadmap.html Porting Matrix
- wiki pages "Debugging DRLVM with ...* for linux and windows
- hints on win/lin specifics here and there. 
I agree that having os info could be great - at least, some notes on
what to do to run on a platform... 

Cheers, 
Nadya
 

>-----Original Message-----
>From: Stefano Mazzocchi [mailto:stefano@apache.org]
>Sent: Friday, December 01, 2006 5:49 PM
>To: dev@harmony.apache.org
>Subject: Harmony on Macosx [was Re: [jira] Created: (HARMONY-2374)
>[classlib][awt] Missing java2d code for OpenGL pipeline.]
>
>Alexey Petrenko wrote:
>> 2006/11/30, Stefano Mazzocchi <stefano@apache.org>:
>>> Oleg Khaschansky wrote:
>>> >> Now, if only I knew how to port all this stuff over to Macosx
:,-(
>>> >
>>> > Porting opengl 2d rendering shouldn't be complicated at all.
Ideally,
>>> > only system-dependent part of the code (which manages opengl
context)
>>> > should be re-implemented using AGL library. There's pbuffer
support in
>>> > AGL, so no problems with blitters (they do use pbuffers already).
>>> >
>>> > But it is not a simple task to port the rest of awt. 2d rendering
is
>>> > just a part of it.
>>> No, I'm talking about porting the entire Harmony codebase not just
>>> this ;-)
>> Didn't you try to run Harmony on OS X with X server?
>
>So, yesterday I got my first Intel-powered mac (which I'm using to type
>now.... faaaaaaaaaaaaast), which means I believe (but then again, I
>might be wrong, it has been years since I wrote any x86 assembly code
>and I have no clue what the core 2 duo instruction set it) might reduce
>the barrier to porting harmony.
>
>So, no, I have not tried it because running harmony on macosx/powerpc
>seemed like too big of a stretch for me to even consider.
>
>> It could help to use Linux codebase I think...
>
>well, certainly I wouldn't have started with the windows one ;-)
>
>> In fact I'm not a Mac OS X guru :(
>
>Right and years ago I would have thought that Intel and Macosx had
>enough impedance mismatch to basically have me to look somewhere else
>for help... but things have changed and I wonder if you guys can find
us
>some macosx expert that might be able to help us with the transition.
>
>btw, macosx shouldn't be that different from freebsd and I know there
>are a lot of freebsd people around the ASF... (and, well, one of the
>original darwin developers is an apache member.. and most apache
members
>use macosx as their OS... question is: how do we get the migration
>started? and how do we convince people it's not that hard?
>
>do we have any documentation about "porting to other system"? I think
>would be immensely helpful.
>
>Thoughts? ideas? suggestions?
>
>I'll try to build harmony on macosx/core2duo today and see how far
along
>I can go before my C/C++/UNIX-linking ignorance creeps in.
>
>BTW, what instruction set is the core2duo anyway?
>
>--
>Stefano.

Mime
View raw message