New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add instructions for building from source using Eclipse 4.2 (Juno) #89
base: master
Are you sure you want to change the base?
Conversation
These are the steps I had to take to get the build to work on Eclipse 4.2, Arch Linux, OpenJDK 1.7.0_15:
This leaves me with 1 sole remaining build error, for which I will open a new issue. |
Development page update with BIRT page and feature name. For the swt jars since the name of the jars depend on the version, I can't commit the changes otherwise it won't compile here. But that's only for a test module and does not impact the deliverables. |
There is a better way of dealing with the SWT issue (taken from this): configure Now, users only need to:
IMHO this far outweighs the small inconvenience of having to download and import an extra (technically redundant) package, as this needs to be done only once. |
Remove platform-dependent jars, add org.eclipse.swt as a required project. This makes the .classpath file contents static. Users need to download and import platform-specific org.eclipse.swt ZIP into their workspace just once, but don't need to .gitignore or fix the .classpath after every Git pull.
So instead of having users change once and for all a classpath file on their machines, now they have to download something else, and thus another step that needs to be documented as been added? I don't see the interest. |
Ah, that explains. I didn't dig into the purpose of that project, I assumed that it was somehow important (why else let the build fail because of it?) |
Which build fails? Not the build on the machine used to build releases, i.e. mine, and that project is not part of the release anyway... |
My build failed. As would anyone else's if using a non-windows non-x86 OS. The build instructions clearly state to import all projects from the Git repo (which is also the most convenient and obvious thing to do in Eclipse), so one would naturally expect them all to build without errors. |
Successfully built and exported feature |
so |
The current instructions, in particular the part about installing the BIRT Charting Engine, refer to Eclipse 3.7. I'm using Eclipse 4.2, and there seem to have been some changes in the naming of things, also I'm not sure about possible compatibility issues.
Open questions:
{-
rant:
I'm not an Eclipse wizard, and neither do I have the intention of becoming one. I just want an IDE for functional programming, and EclipseFP works well (in Eclipse 4.2) for that. I have spent more time trying to fix all kinds of weirdness in Eclipse than I'd care to admit, and in the time it would have taken me to fix them all, I could have easily constructed a complete proof of Fermat's Last Theorem (just joking!)
You get my drift (I hope) :-)
-}