From dev-return-20769-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org Fri Dec 01 15:06:25 2006 Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 34915 invoked from network); 1 Dec 2006 15:06:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Dec 2006 15:06:23 -0000 Received: (qmail 40821 invoked by uid 500); 1 Dec 2006 15:06:29 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 40785 invoked by uid 500); 1 Dec 2006 15:06:28 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 40776 invoked by uid 99); 1 Dec 2006 15:06:28 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Dec 2006 07:06:28 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.55.52.88] (HELO mga01.intel.com) (192.55.52.88) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Dec 2006 07:06:16 -0800 Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by mga01.intel.com with ESMTP; 01 Dec 2006 07:05:55 -0800 Received: from fmsmsx334.amr.corp.intel.com ([132.233.42.1]) by fmsmga001.fm.intel.com with ESMTP; 01 Dec 2006 07:05:55 -0800 X-ExtLoop1: 1 X-IronPort-AV: i="4.09,485,1157353200"; d="scan'208"; a="171645728:sNHT20783217" Received: from nnsmsx411.ccr.corp.intel.com ([10.125.16.19]) by fmsmsx334.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 1 Dec 2006 07:05:55 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Harmony on Macosx [was Re: [jira] Created: (HARMONY-2374) [classlib][awt] Missing java2d code for OpenGL pipeline.] Date: Fri, 1 Dec 2006 18:05:48 +0300 Message-ID: <523F3D8D8C97554AA47E53DF1A05466A6D9917@nnsmsx411.ccr.corp.intel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Harmony on Macosx [was Re: [jira] Created: (HARMONY-2374) [classlib][awt] Missing java2d code for OpenGL pipeline.] Thread-Index: AccVV97QulALUbIARX6gES6byTJtqgAADreA From: "Morozova, Nadezhda" To: X-OriginalArrivalTime: 01 Dec 2006 15:05:55.0356 (UTC) FILETIME=[3332DDC0:01C7155A] X-Virus-Checked: Checked by ClamAV on apache.org >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.=20 I agree that having os info could be great - at least, some notes on what to do to run on a platform...=20 Cheers,=20 Nadya =20 >-----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 : >>> 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.