Opened 8 years ago
Closed 8 years ago
#108 closed defect (invalid)
Mono not detected when installed on Mac
| Reported by: | Iritscen | Owned by: | Alloc |
|---|---|---|---|
| Priority: | critical | Component: | AEI2 |
| Keywords: | Cc: |
Description (last modified by Iritscen)
Over the last few months, there were various issues with Mono installing in 10.11. I believe all those have been cleared up by the developers. However, the AEI is now failing to detect Mono when it is installed. The install directory was moved from /usr/bin/ to /usr/local/bin/ to work with 10.11, but that shouldn't make a difference.
I see that the AEI is simply running "which mono" and checking the output to see if it looks like a path. This should work; on my Macs, I can run "which mono" in Terminal and get "/usr/local/bin/mono" as output, but the AEI does not seem to be getting this output when it runs the command. The result is that it tells the user to install .NET and quits.
This bug seems to be occurring in not just 10.11, but also 10.9 (therefore probably all OS versions).
Change History (2)
comment:1 Changed 8 years ago by Iritscen
- Description modified (diff)
comment:2 Changed 8 years ago by Iritscen
- Resolution set to invalid
- Status changed from new to closed
Somehow I failed to realize that the environment being used to invoke Java from the Mac AE launch shortcut app does not have the extended PATH variable that is present in the Terminal environment. The "AppleScript" environment (default Unix environment?) does not include /usr/local/bin/, where Mono is now installed due to 10.11's security restrictions, so "which mono" could not possibly work for the AEI. I have updated the Mac AE Setup to include a fixed launch app that extends PATH when calling the AEI's .jar.