GSoC 2015 Idea Discussion

[Clemens Lang]

Hi,

----- On 9 Mar, 2015, at 10:13, René J.V. Bertin rjvbertin at gmail.com wrote:

> All of Xcode? Doesn't that block access to the SDKs too, and is that going to
> require the use of a compiler installed through MacPorts?

I don't know. It's part of the task to find out. Somehow the Command Line Tools
succeed in producing working code without an Xcode installation and don't ship
an SDK, so I'm assuming they are not needed for most ports.


> I can see the use for not requiring the (obscenely huge) Xcode for the average
> MacPorts user, but why would those of us who need Xcode anyway be obliged to
> install another compiler for the probable majority of ports that build just
> fine with Apple's compiler?

Nobody would be obliged to do that. The Command Line Tools are already a
requirement for MacPorts and would still be available. This is not about
removing the dependency on *any* compiler provided by Apple, but removing
(or rather, explicitly declaring) dependencies on Xcode. This way, we could
print a good error message rather than have a build fail when a user doesn't
have Xcode but tries to install a port that needs it.

-- 
Clemens Lang