Three questions about speeding up macports builds.

[Ryan Schmidt]

Remember to Reply All so the conversation stays on the list.


On Apr 18, 2019, at 14:06, Christian Calderon wrote:

> It seems that I can't run a non-App Store installed Xcode in Mojave, which is a bummer.

I haven't upgraded to Mojave yet so I don't have experience with it. Note that MacPorts doesn't need to "run Xcode"; it just uses files that happen to be installed along with Xcode, such as xcodebuild, the clang and gcc compilers, include files, libraries, macOS SDK files, etc.. It seems unlikely to me that Mojave would be able to deny you access to those files, assuming you have been able to install them. (And system integrity protection or expired certificates may prevent you from installing them.) However, I don't believe you will have much success trying to run older compilers on a newer system. For one thing, those older compilers expect to find their libraries and includes in /usr, which is an OS directory; you don't want to pollute a new OS's directories with bits from older OS versions. That may have adverse consequences for the new OS.


> I do have a 2010 Mac Pro that I could install Leopard on though. I think I will try doing that.

The current OS version in 2010 was Snow Leopard. You should not expect to be able to boot a Mac with an older OS version that doesn't know about that Mac model. But you could do it in a virtual machine. All of our Intel-based automated builders are virtual machines running in VMware ESXi on Xserves. Note that to virtualize 10.5 or 10.6, you need the special Mac OS X Server version of the OS.