Bugzilla – Full Text Bug Listing
| Summary: | Eclipse can't find program .so files under install directory | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Reza Rahman <reza> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 2.0.2 | ||
| Target Milestone: | 3.0 | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
|
Description
Reza Rahman
Sorry, in the example scenario above I meant /usr/local/eclipse/eclipse NOT usr/local/eclipse/eclipse. Related to bug 26756. Work-around is to cd to the directory that Eclipse is installed and then use the "-data myWorkspaceLocation" command-line argument. Are the command line options documented somewhere? How does this solve the shortcut problem? Should I add the -data option to all shortcuts? dev.eclipse.org -> Projects -> The Eclipse Project -> documentation -> Workbench User Guide -> 2.0 Documentation -> Tasks -> Running Eclipse I believe for now you must modify your shortcut or add the directory with the Eclipse libraries to your path. We are investigating a solution to related bug 26756 but it won't be available for 2.1. Unfortunately, I have already tried to add the files to my path to no avail. It seems Eclipse does not search the path or any other environment variable. I will try to modify the shortcut (launcher in RH Linux 8) to say /usr/local/eclipse/eclipse -data \home\reza. Hopefully, that will do the trick. Do you know of a way Eclipse can be "fooled" into believing it was invoked from its installation director using RH Linux launchers? Sorry, I'm not sure how to fool it. To be honest, I use a script which passes in all the command-line args which I use. Can you please tell me how the script looks like and how you launch it? I do things a little differently. I run from a console and use -consoleLog so anything written to the log file is written to the console and grabs my attention so I can enter bug reports. In any case, here is what I use: ./eclipse -vm /home/dj/ibm131sr2/jre/bin/java -data /home/dj/target/head/plugins/ -consoleLog -showlocation & As I suspected, specifying a workspace with -data does nothing to start eclipse out of its installation directory. I still can't believe that something like this was overlooked while developing. As far as I am concerned, this is a bug that needs to be fixed. In the meanwhile, if I can invent a workaraound, I will post it here... Here is a workaround (it is not pretty but it works): create a script somewhere in your path like so: cd [ECLIPSE INSTALL DIRECTORY] ./eclipse -data $PATH Let us assume the name of this script is run-eclipse and it is granted execute permission. If you expect this script to run eclipse, it won't work as cd commands do not work as you expect them to in shell scripts. In order to get things to work, you will need to create yet another wrapper script. Here it is: . run-eclipse (in bash and c-shell) OR source run-eclipse (in bourne shell) Now, save this script somewhere in your path as eclipse. Wherever you invoke this script from, eclipse will run as you would expect it to. You can even use it as a RedHat Linux 8 launcher command... Have fun! Was this bug solved in the new release? |