Closed GoogleCodeExporter closed 9 years ago
It turns out applications not started from the terminal use a different PATH
configuration. This means we can't expect tools installed via MacPorts to work
without customizing our bundle.
Fortunately, the info.plist file in the bundle accepts custom environment
variables. With this we can set the path to include the usual defaults and any
other places the utilities might install. For now, this will be /opt/local/bin,
since that is where MacPorts installs stuff. I will have to look into whether
there are other places the utilities might be installed (through other
services, such as Fink).
Original comment by xander4j...@yahoo.com
on 7 Apr 2013 at 4:34
I have it working now using application-specific environment variables as
described above.
Original comment by xander4j...@yahoo.com
on 8 Apr 2013 at 2:27
Original issue reported on code.google.com by
xander4j...@yahoo.com
on 4 Apr 2013 at 4:42