chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH] fix Mac OS X build


From: Jim Ursetto
Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build
Date: Tue, 28 Jan 2014 13:58:00 -0600

On Jan 28, 2014, at 1:53 PM, Felix Winkelmann <address@hidden> wrote:

> From: Jim Ursetto <address@hidden>
> Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build
> Date: Tue, 28 Jan 2014 13:10:53 -0600
> 
>> Do you mean, why isn't it in the README for Chicken? 
> 
> Yes, that's what I meant.
> 
> I think it is a recent change, prior to XCode 5 AFAIK the shims were always 
> installed in /usr/bin automatically.  
> 
> Not in Xcode4, as I'm quite sure, since I had quite some trouble figuring out 
> the
> correct locations.

That is possible.  I never had to do anything special with XCode 4 as far as I 
remember; the binaries were always in /usr/bin.

> If the user uses xcode-select to switch to another toolchain, then an already 
> installed
> chicken/csc/chicken-install will not find the correct tools. So I see no 
> other way
> than hardcoding the paths. 

I don't see why not.  chicken should be using /usr/bin as its binary directory, 
and so when xcode-select changes the install location, it will still work.   (I 
think the shims just look up the actual XCode location and then exec() it -- 
they're not symlinks nor are they physically updated in place, AFAIK.)  Am I 
missing something?

Jim


reply via email to

[Prev in Thread] Current Thread [Next in Thread]