Re: Build rule "depends on itself?"
Re: Build rule "depends on itself?"
- Subject: Re: Build rule "depends on itself?"
- From: Michael Rawdon <email@hidden>
- Date: Thu, 12 Aug 2004 17:44:33 -0700
Hi Glen -
On Aug 12, 2004, at 5:04 PM, Glen Low wrote:
One of the hairier pieces of Graphviz has a few custom build rules in
it. I'm glad to say that when Xcode 1.5 works, it works far better at
resolving dependencies with custom rules than 1.2, however it
occasionally fails to even build with this error:
Dependency analysis: File </ ... /
graphviz.build/gvpr.build/Script-343042a0.sh> depends on itself. This
target might include its own pro...
I can get it to build sometimes by changing the order of output files
in one particular build rules, but then the next time it builds it
fails again.
How do I go about getting a permanent fix? I can't actually see the
mentioned script file so I can't diagnose that.
The script file probably refers to a shell script build phase or custom
build rule. You could examine the file in an editor and see if you can
match it to such a script.
That said, the main instance in which this warning has been encountered
involved a circular dependency. The canonical example we unearthed was
a target which included its own build product in one of its build
phases. But there may be other instances we don't know of yet. If you
discover another concrete example, then we'd certainly be interested in
a bug report on it.
(Just to be clear, this sort of problem is not new. For instance, if
you ever saw Xcode get confused about whether the build failed or
succeeded in Xcode 1.2 or earlier, that was another failure mode of the
same problem. We're trying to both make it harder to get into bad
states like this, but also provide more comprehensible failure modes.
But obviously there's more to shake out.)
Also, there seems to be a cosmetic bug where when you select "Custom
script:" from the build rule drop down, it changes to "Unknown
compiler com.apple.compilers.proxy.script". Don't know yet whether
this is an artifact from an old upgraded project from 1.2 or something
else.
This is a flat-out glitch in 1.5 which is already in our bug system.
Thanks for letting us know, tho!
--
Michael Rawdon Apple Computer, Cupertino CA
Xcode Developer email@hidden
"If you can't be a good example, then you'll just have to be a horrible
warning."
- Catherine Aird
_______________________________________________
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.