From owner-freebsd-eclipse@FreeBSD.ORG Thu Apr 27 07:23:11 2006 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEDD316A405 for ; Thu, 27 Apr 2006 07:23:11 +0000 (UTC) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (fly.ebs.gr [83.171.239.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF69E43D45 for ; Thu, 27 Apr 2006 07:23:09 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id k3R7N34F094640; Thu, 27 Apr 2006 10:23:03 +0300 (EEST) (envelope-from past@ebs.gr) Received: from [10.1.1.185] (pc185.ebs.gr [10.1.1.185]) by ebs.gr (8.13.3/8.13.3) with ESMTP id k3R7NHla020733; Thu, 27 Apr 2006 10:23:20 +0300 (EEST) (envelope-from past@ebs.gr) Received: from 127.0.0.1 (AVG SMTP 7.1.385 [268.4.6/324]); Thu, 27 Apr 2006 10:22:59 +0300 Message-ID: <44507153.2000005@ebs.gr> Date: Thu, 27 Apr 2006 10:22:59 +0300 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Georg-W. Koltermann" References: <1146086591.42187.2.camel@localhost.eu.mscsoftware.com> In-Reply-To: <1146086591.42187.2.camel@localhost.eu.mscsoftware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-eclipse@freebsd.org Subject: Re: anyone working on Eclipse 3.2? X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2006 07:23:12 -0000 Georg-W. Koltermann wrote: > I wanted to take a peek at Eclipse 3.2(RC), but when I run it with the > Linux jdk 1.5 I soon get a core dump :-( > > So, is anyone already working on a FreeBSD native version? Any > preliminary work that you could share? I'm planning to do it eventually, if no one beats me to it (which I would really appreciate :-)). My usual strategy, is to copy eclipse over to eclipse-devel, modify the distfile and version stuff and keep the patch files. Then it is a boring sequence of make patch -> error -> redo the patch that failed. I believe some of our patches may no longer be necessary, like manualpatch-plugins-swt-gtk-os_custom.h and manualpatch-plugins-swt-cairo-library. After our current patches apply correctly, there is a new sequence of make -> error -> create new patches. I hope that helps. Cheers, Panagiotis