Re: Groups, shell scripts, yacc
Re: Groups, shell scripts, yacc
- Subject: Re: Groups, shell scripts, yacc
- From: Glen Low <email@hidden>
- Date: Sat, 22 Nov 2003 07:34:26 +0800
3. It seems yacc support is broken, the generated parser_yacc.sh
script has the wrong paths for the derived sources. Any clues to a
workaround? In particular, can you (and how do you) do a selective
override of particular target rules?
My workaround is simple, add :
HEADER_SEARCH_PATHS = "$(DERIVED_FILES_DIR)/Yacc"
Thanks for the tip, but it doesn't seem to work, since the problem is
with the generation of headers and sources, not the inclusion of them
in subsequent compiles.
4. It doesn't seem sufficient to add a internal, dependent framework
on to the target's Frameworks and Libraries, you need to add it to
the Direct Dependencies if you want a rebuild triggered when the
dependent framework changes?
Yes you have to add the .pbproj or .xcode project to the project as a
file, hence Xcode is aware of the targets present in this specific
project, and then you add the depenedencies on the inspector of the
target. I think that it is due to the fact that your project can
contain a bunch of target :)
I was adding the product, which was in red until I actually built it,
to the other project's Frameworks and Libraries, which works swimmingly
until you update the project, which doesn't trigger a rebuild in the
other project. So effectively I'm adding a single target only, and if
Xcode could track single file dependencies it should be able to figure
out what gets affected by the single target change.
Cheers, Glen Low
---
pixelglow software | simply brilliant stuff
www.pixelglow.com
_______________________________________________
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.