Embarassingly, it turns out at some point I created a /usr/include/X11 -> /usr/X11R6/include/X11 symlink on my dev system and this masked an issue in the original Eclipse 4 tarball I sent out. Attached tarball has been corrected for this. (You still need the "eclipse-natives" distfile from the original mail.)
On Fri, May 04, 2012 at 02:57:22PM -0700, Matthew Dempsky wrote: > Attached is a port for Eclipse SDK 4.1.2. I've only tested it on > amd64, but it should (might?) work on i386 too. For the time being, > there's no upstream for the "eclipse-natives" distfile, so just add > the attached copy directly to your distfiles directory. > > Once installed, Eclipse should "Just Work". The eclipse executable is > located at /usr/local/eclipse4/eclipse, and you'll need to make sure > /usr/local/jdk-1.7.0/bin is on your PATH and possibly bump your memory > limits too. > > Please let me know if you find anything that doesn't work correctly. > > > Background: > > After spending weeks of frustration trying all of the different build > options available for Eclipse SDK, I finally made a break through with > a hacky solution that actually works reasonably well IMO: simply take > the official Eclipse Linux binary distribution tarball and then swap > out the handful of Linux native code files with appropriately compiled > OpenBSD replacements. > > Because there doesn't seem to be any convenient place to fetch the > native libraries source code from, I decided to write a simple > "make-natives-snapshot.sh" that downloads the minimal code needed from > the Eclipse's git repositories and then creates a timestamped tarball. > > There are ways the package could likely be improved (e.g., install the > native libraries in /usr/local/lib/eclipse4 or something rather than > stuffing them back into Eclipse's bundled jar files, or splitting out > the xulrunner and webkit dependencies into separate subpackages so you > don't need both), but I'm erring on the side of simplicity for now.
eclipse4-sdk.tar.gz
Description: application/tar-gz
