[arch-dev-public] Eclipse: planning a switch to binaries
All, After much of my hair is missing on account of tearing it out (David Rosenstrauch's too) trying to get everything we want out of an Eclipse build-- or even just a version that can consistently build-- I'm planning to switch main eclipse over to the prebuilt binary. Why? Here's the reasons: 1) Better compatibility. The eclipse foundation uses something like 7 JVMs in their build process, and builds everything for optimal compatibility. 2) The eclipse foundation's build process is "too complicated for you" and can't be recreated by mere mortals. 3) The annoying "Assembling..." bug that has plagued us for years and causes only 1 out of every 5-10 attempts to make eclipse to actually work. 4) No clear benefit (possibly a little sacrificed speed) of continuing to build from source. So I'm waiting until Wednesday (7/3) to hear counterpoints on this, and then switching the main eclipse and eclipse-cdt packages over to build from eclipse foundation binaries. Please register your feedback here! Best, Paul
On Mon, 30 Jun 2008, Paul Mattal wrote:
All,
After much of my hair is missing on account of tearing it out (David Rosenstrauch's too) trying to get everything we want out of an Eclipse build-- or even just a version that can consistently build-- I'm planning to switch main eclipse over to the prebuilt binary.
Why? Here's the reasons:
1) Better compatibility. The eclipse foundation uses something like 7 JVMs in their build process, and builds everything for optimal compatibility.
2) The eclipse foundation's build process is "too complicated for you" and can't be recreated by mere mortals.
3) The annoying "Assembling..." bug that has plagued us for years and causes only 1 out of every 5-10 attempts to make eclipse to actually work.
4) No clear benefit (possibly a little sacrificed speed) of continuing to build from source.
So I'm waiting until Wednesday (7/3) to hear counterpoints on this, and then switching the main eclipse and eclipse-cdt packages over to build from eclipse foundation binaries. Please register your feedback here!
Best, Paul
Are there binaries available for x86_64? If not, that could be a problem. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Eric Belanger wrote:
Are there binaries available for x86_64? If not, that could be a problem.
Both are provided. - P
I'm all for freeing up your time to do anything more productive than battling with build procedures. Like ... anything. // jeff -- . : [ + carpe diem totus tuus + ] : .
2008/7/1 Simo Leone <simo@archlinux.org>:
On Mon, Jun 30, 2008 at 10:11:39PM -0400, Paul Mattal wrote:
Eric Belanger wrote:
Are there binaries available for x86_64? If not, that could be a problem.
Both are provided.
I thought eclipse was written in Java.
Same here. :-P The reasons are reasonable and there is x86_64, so another +1 here. -- Roman Kyrylych (Роман Кирилич)
On Mon, 2008-06-30 at 23:11 -0500, Simo Leone wrote:
On Mon, Jun 30, 2008 at 10:11:39PM -0400, Paul Mattal wrote:
Eric Belanger wrote:
Are there binaries available for x86_64? If not, that could be a problem.
Both are provided.
I thought eclipse was written in Java. Anyway, +1 on just using their binaries.
-S
At least for swt there's bindings to native system libraries. In case of mozilla/xulrunner I don't think they will link correctly with xulrunner 1.9. If this really is the case, we could always rebuild just swt from source and use the binary eclipse. We'll build a standalone swt package from source anyways.
On Mon, 30 Jun 2008, Paul Mattal wrote:
Eric Belanger wrote:
Are there binaries available for x86_64? If not, that could be a problem.
Both are provided.
- P
In that case, no objections from me if that can make your job easier. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
participants (6)
-
Eric Belanger
-
Jan de Groot
-
Jeff Mickey
-
Paul Mattal
-
Roman Kyrylych
-
Simo Leone