| Re: [eclipse-dev] Eclipse startup OSX |
| We have this problem in PTP also. If you have compilers or other external tools installed in a non-standard* place, then Eclipse will typically not be able to find them. Even though this is standard OSX behavior, it is a barrier when trying to use Eclipse as a development platform. In Xcode, everything just works without requiring any configuration, for example. The problem is there is no simple solution. Even if it were possible to use a wrapper script, there are users who use csh rather than bash, so their path will still not be correct. Worse, the relatively simple solution that worked for Lion no longer works for Mountain Lion: http://wiki.eclipse.org/PTP/FAQ#Q:_Eclipse_doesn.27t_seem_to_find_commands_for_.5Bcompiler.2C_make.2C_....5D We would be very interested in a (simple) solution to this problem, but unfortunately there doesn't seem to be any. Regards, Greg * anything other than /usr/bin, /bin, /usr/sbin, or /sbin. On Aug 6, 2013, at 9:26 AM, Doug Schaefer <DSchaefer@xxxxxxx> wrote:
| ||