Mac build support is missing

Mac build support is missing when I try to install Unity 5.5 or 5.6
But if I install Unity 5.3.5 it is exists.
Whats wrong with Unity installer?
I tried to restart even whole Mac.

 

I don't recall for sure, but it might be that when you're installing the Mac version of Unity, you get Mac build support automatically now, so it's no longer an option.

You might just finish the install and see.

 

Thank you for answer.
I tried but it is not support Mac

 

Beside this, why can't we build for Mac or Linux from a PC, for PC and Linux from a Mac and for Mac and PC from Linux?

 

Correct.

You can, and always have been able to. (Since Unity became cross-platform anyway...waaaaaaay back near the beginning, Unity was Mac-only and building for Windows required the Pro license.)

As for the actual problem, I haven't encountered it, but the top result of a quick search found this as a possibility.

--Eric

 

Thank you @Eric5h5
Problem was not in Unity. Problem was in the project.

I tried to delete EditorBuildSettings.asset and even clear whole ProjectSettings folder not help.
Helped only creating new project and importing all assets and ProjectSettings folder.

 

I solved "the problem", downloading the UNITY INSTALLER, for me was that. I didn't know that i have to download each module in the INSTALLER VERSION instead of the EDITOR version. Just in case anyone is having the same problem or trouble. Check that first... because is was an EASY fix.

 

In the Linux version, I can't seem to install the OSX build support. I tried to reinstall Unity several files, but no OSX toolchain in the Editor...

 

To fix the Linux can't build to OSX build support -> there is an issue in the following file ->

Code (csharp):

1. ../Hub/Editor/-version-/modules.json

in the

Code (csharp):

1. {"id":"mac-mono"

section, you need to update the

Code (csharp):

1. {UNITY_PATH}

to

Code (CSharp):

1. {UNITY_PATH}/Editor/Data/PlaybackEngines/MacStandaloneSupport

you may also need to set selected to false.
make the change with hub closed, reopen it and read the build target

I have been having to do this for ever unity version for a while. Given that it is a simple modules.json file fix, I don't know why we have gone multiple versions of unity without it getting fixed.

 

@PixelJ, sorry about the slow response, yes it has been reported and has an open bug file.

https://issuetracker.unity3d.com/is...pseudo-installed-through-hub-for-linux-editor

as I said, since the whole issue is a few characters in a config file, still not sure why this hasn't been fixed.

 

Can I take the honor of bumping this? We're on 2019.3 and this is still an issue. I would've thought the heavy market of Mac users would've demanded this bug be fixed sooner?