MacPorts tends to work fine without Xcode unless a package needs xcodebuild.
On Nov 20, 2014, at 10:41, René J.V. Bertin rjvber...@gmail.com wrote:
MacPorts should do fine with the commandline tools, no? (xcode-select -p
/Library/Developer/CommandLineTools)
On Nov 20, 2014, at 10:44 AM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
MacPorts tends to work fine without Xcode unless a package needs xcodebuild.
On Nov 20, 2014, at 10:41, René J.V. Bertin rjvber...@gmail.com wrote:
MacPorts should do fine with the commandline tools, no?
Hi,
Tends to work, yes. We don't support that configuration, so just hope you
don't run into any problems with it.
another data point might be interesting here. During the upgrade to Yosemite
I rebuilt all of my ports without Xcode and the 10.10 SDK in trace mode.
All of my 500+ ports either
Hi,
I've seen lots of talk about XCode 6 lately. When I had my 10.9.4 VM running
the last few days, I did get an update for the dev. command line tools (to 5.1
IIRC), but no sign of an update to the IDE. Would that require upgrading to
10.9.5 first?
Cheers,
René
In article 1977346.HivKc7Tkja@portia.local,
I've seen lots of talk about XCode 6 lately. When I had my 10.9.4 VM running
the last few days, I did get an update for the dev. command line tools (to
5.1 IIRC), but no sign of an update to the IDE. Would that require upgrading
to 10.9.5 first?
On Sunday November 16 2014 16:07:21 Ned Deily wrote:
The Xcode entry in the Mac App store claims that 10.9.4 or later is
required for the current Xcode 6.1. You may need to login in the App
Store app to buy it (for free) if you haven't already or to ensure
your account is registered on
