Re: Updating Bison
Re: Updating Bison
- Subject: Re: Updating Bison
- From: Fritz Anderson <email@hidden>
- Date: Thu, 10 Apr 2014 12:05:53 -0500
On 10 Apr 2014, at 8:48 AM, McLaughlin, Michael P. < email@hidden> wrote:
Xcode 5.1 uses Bison 2.3. Is it safe to replace
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/bison
with Bison 3? If so, would a subsequent Xcode update override this with an older version of Bison?
Jens’s solution is probably better, because it should solve things in every case. (Unless the Xcode build system uses its own $PATH?)
What I think might work (haven’t tried) is to select Build Rules in the Target editor, duplicate the Yacc rule, and use the Custom Script to substitute the hard/linked path to your bison.
If you need a non-standard suffix, there’s a "names matching" option. I wonder if it takes a regex/glob pattern. But that’s target-by-target.
— F
-- Xcode 5 Start to Finish. This time, it’s leashed.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
| References: | |
| | >Updating Bison (From: "McLaughlin, Michael P." <email@hidden>) |