• 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
lex: Found my answer, never mind
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lex: Found my answer, never mind


  • Subject: lex: Found my answer, never mind
  • From: Dan Caugherty <email@hidden>
  • Date: Tue, 22 Sep 2009 21:56:58 -0400

Hey all --

Sorry to bother again, but I just found my answer. For posterity's sake:

Inspecting the target in question (Command-I) reveals the magic pop-up
for build rules. So I defined one for Lex (.l) files for this target
to use the following custom script:

lex -+ --yyclass=${INPUT_FILE_BASE}
-o${DERIVED_FILES_DIR}/lex.${INPUT_FILE_BASE}.cpp ${INPUT_FILE_NAME}

with the following output file:

lex.$(INPUT_FILE_BASE).cpp

..and things seem to be rather copacetic now.

Cheers,
-- Dan
 _______________________________________________
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

  • Prev by Date: lex: how to override Xcode's output file choice?
  • Next by Date: Re: Different library per build configuration?
  • Previous by thread: Re: lex: how to override Xcode's output file choice?
  • Next by thread: Xcode3.2-IB: No outlet/action section in inspector panel (identity)
  • Index(es):
    • Date
    • Thread