- How to find mono framework on mac install#
- How to find mono framework on mac update#
- How to find mono framework on mac mac#
I installed it to /Volumes/osxapps/ instead of root, but the installation still expected everything to be in root. I recently installed mono from MonoFramework-MDK-4.8.0.pkg. ( Commands is a symbolic link to bin, but it still may not work) It will automatically add /Library/Frameworks/amework/Versions/Current/Commands to $PATH, but I don’t know if you will need to add /Library/Frameworks/amework/Versions/Current/bin/ by hand or if everything just works.
How to find mono framework on mac install#
7:Ītm, the mono framework installer only works correctly if you install it to root. The GM release has already disabled the NVRAM workaround, so this answer should get you what you need moving forward. Note: Previous answers around the Internet about this problem give you instructions for modifying NVRAM settings, but Apple stated that the NVRAM method would stop working with El Capitan’s public release. Those typically need to install files into /usr/include and /usr/lib, which are also now restricted. I ran into a problem with the same root cause while trying to get pear/pecl modules and macports/homebrew apps installed. When you’re done, it is highly recommended that you re-enable SIP by following the same steps, but using csrutil enable in step 3. Reboot and run the command that worked prior to El Capitan Reboot into recovery mode (reboot and hold down Cmd-R).If you run the command ls -lO /System/Library/LaunchDaemons you’ll see that the directories and files under there are now marked as “restricted.”
6:Įl Capitan now protects certain system directories in “rootless” mode (a.k.a. Anyone with actual programming experience to comment or clarify? Solution no. Since I’m not a programmer or coder (at least not for a long time and never on OS X), this allowed me to run Duplicati using mono (which was why I wanted it in the first place), but I’m not sure if this is the correct way to solve this or even if this should be done at all. I am not sure which mono 4.x release that started in…īut I would assume that you do not have /usr/local/bin in your path(?), try: export PATH=/usr/local/bin:$ Newer versions of mono comply to the “El Capitan” requirements of not installing anything into /usr/bin and thus now /usr/local/bin is used. So /usr/local/bin is no longer used… Original The latest versions of Mono (5.x) installation process creates a file ( mono-commands) in /etc/paths.d that contains the path of: /Library/Frameworks/amework/Versions/Current/Commands
How to find mono framework on mac update#
1: Update (since this is still getting views two+ years later): …but it isn’t present in /usr/bin and attempting to find its executable using which mono returns nothing. Lrwxr-xr-x 1 root wheel 60 Sep 9 22:16 amework -> /System/Library/PrivateFrameworks/ameworkĭrwxr-xr-x 5 root wheel 170 ameworkĭrwxr-xr-x 8 root wheel 272 Sep 9 22:19 amework /Applications/Motion.app/Contents/Frameworks/AudioMi圎ameworkĭrwxr-xr-x 8 root admin 272 Sep 12 11:24 amework Lrwxr-xr-x 1 root wheel 74 AudioMi圎amework ->. /Applications/Motion.app/Contents/Frameworks/amework
The mono framework does appear to be installed: Lees-Mac-Pro:Downloads kevinmack$ cd /Volumes/Macintosh\ HD/Library/Frameworks/ The installer appeared to complete successfully, but an attempt to call mono returns To install it, I ran uninstallMono.sh as root to ensure we didn’t have any leftover cruft, then ran MonoFramework-MDK-4.0.4.1.
How to find mono framework on mac mac#
I’m trying to get a Mono install running on a mac (OS X version 10.10.5), and while the install states that it’s completed successfully, I’m not able to call mono from the terminal.