From: Jim Ursetto <[email protected]> Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build Date: Wed, 29 Jan 2014 04:28:11 -0600
> On Jan 29, 2014, at 2:33 AM, Felix Winkelmann <[email protected]> > wrote: > >> From: ".alyn.post." <[email protected]> >>> I agree with Jim here. I don't use Xcode, but need gcc/clang for brew, >>> chicken, &c. I benefit from this project: >>> http://kennethreitz.org/xcode-gcc-and-homebrew/, which provides gcc >>> and associated darwin libraries on the command-line. My gcc is in >>> /usr/bin, which got that way installing brew, for which I assume I >>> did something similar to/identical to the instructions upthread. >>> >>> So I have a proper compiler in /usr/bin, and I'd like chicken to >>> continue to use it. >> >> You are free to do so, by overriding the appropriate build-variables. Yet, >> why >> shouldn't the default build play it safe? > > Well, no one else appears to be having any issues right now, so I would argue > using /usr/bin/gcc is playing it safe. I would also argue that hardcoding > paths into the XCode directories is a fringe use case. So, please explain > exactly what problem you are having, along with your OS version and XCode > version. I think I have explained the problem sufficiently. What happens if the user switches the xcode-version via "xcode-select" _after_ chicken has been installed? I think this is a genuine problem, in particular since xcode-select makes it easy to do so, and someone involved in iOS app-development might actually have to switch between Xcode versions several times. I did, because I had to make sure an app survived the transition from iOS6 to iOS7, and between Xcode4 and Xcode5. But I didn't use xcode-select, because, dumbshit as I am, I didn't know about it, and, because even if I had, I would have tried to avoid it, to get around the exact issue I'm talking of. felix _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
