|headless build for use with eclim [message #64030]
||Thu, 04 June 2009 03:26
Registered: July 2009
I'm trying to build a headless eclipse build for use with eclim (vim and
eclipse combined) and am finding a maze of different tarballs,
interlocking builds, and bugs in the build. So:
- assuming I want C, C++, and java development support, which tarball
should I be downloading? (I'd rather be building from scratch, because I
keep binaries in a non-standard location)
- why is this so difficult? Is there a 'one in all' build platform?
And why isn't there a standard build.xml, with one ant build and target to
create all that I need?
I swear, building gcc is easier than building eclipse.. At least I know
which tarball to download in that case. And I don't get errors like:
[javac] 1. ERROR in
/home/edp/work/tst/third_party/support/build/eclipse-3.4.2/p lugins/org.eclipse.osgi/osgi/src/org/osgi/framework/AdminPer mission.java
(at line 1)
[javac] The type java.lang.Object cannot be resolved. It is indirectly
referenced from required .class files
out of the box, where java seems to go braindead and not even recognize
its own 'Object' class.
Any help with this would be great - but best of all would be an
out-of-the-box script on unix which builds this stuff from scratch without
need for eclipse to build it.
Thanks much - any help appreciated - you can reach me at
Powered by FUDForum
. Page generated in 0.01954 seconds