• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Yacc support in Xcode broken ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Yacc support in Xcode broken ?


  • Subject: Yacc support in Xcode broken ?
  • From: Olger Warnier <email@hidden>
  • Date: Fri, 7 Nov 2003 11:41:16 +0100

Hi Pascal,

I found the same issues with the yacc support and tried to make a
custom rule for it.
Go to your target settings, rules and with the (+) below you can add
your own rule. Choose the custom build script.
I am stuck at that point, not knowing how to define these rules.

Does any happen to know if the known variables (like $(TARGET_NAME) )
work in these custom rule definitions and if there are options to refer
to the current file being compiled ?
I'd like to use bison instead of yacc with some additional rules
and need something like: bison -y $(current y file) -p eval -l -d -o
$(currentfilenamewithoutext)


> Subject:
> Yacc support in Xcode broken ?
>
> To:
> email@hidden
>
> From:
> p3consulting <email@hidden>
>
> Date:
> Tue, 4 Nov 2003 18:52:01 +0100
> Does somebody has encountered this problem and was able to solve it or
> is this a bug to be filled:
>
> I have a project - converted from PB - with .y file in it.
> it used to compile fine in PB, however in Xcode, the generated shell
> script is buggy:
>
> cd build/FuseConsole.build/iacsparser.build/DerivedSources/Yacc &&
> /usr/bin/yacc -d
> /Volumes/Development/ProjectBuilder/JCConsole/jcconsole/iacs.y && cp
> y.tab.h
> build/FuseConsole.build/iacsparser.build/DerivedSources/Yacc/iacs.h &&
> cp y.tab.c
> build/FuseConsole.build/iacsparser.build/DerivedSources/Yacc/iacs.c
>
> the "cp's" fail because of the destination path being repeated in the
> destination file description when we are already in that directory due
> to the initial "cd" command.
>
> I don't find any way to change the behavior of this by changing build
> settings (the script is auto-generated by the build process), is there
> a way to correct this ?
>
> So far the only solution I have found is to remove the .y file from
> the target and add a shell script build phase of my own, the resulting
> .c and .h files being added to the target, 
> (sad solution but it works)
>
> Any idea out there ?
>
>
>
>
>
> Pascal Pochet
> P3 Consulting
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Yacc support in Xcode broken ?
      • From: Gerard Iglesias <email@hidden>
  • Prev by Date: Re: Public Headers in Xcode?
  • Next by Date: dylib unittesting and custom executables
  • Previous by thread: Yacc support in Xcode broken ?
  • Next by thread: Re: Yacc support in Xcode broken ?
  • Index(es):
    • Date
    • Thread