The call to DBCopyBuildInheritance actually packages up that array of builds by iterating over the inherits property, which you then go back and break apart to print the file format. So that API call is wasted effort. I wrote a shorter piece of code which goes directly to DBCopyOnePropString(). I believe its functionally equivalent to your submission, but a little simpler code-wise. However, there's probably a cleaner way to separate out the actual dot-format text (and the printing there of). And I might be missing some cases, so please test and let me know. Thanks -Bill On Jan 14, 2008, at 3:24 PM, Michael Franz wrote:
Hi all,
Here is the latest version of the dot plugin. I am not so happy with the logic, but it works.
What this does it create a dot output (stdout) of the relationship between all loaded plists. Nothing fancy.
Michael <dot.c>_______________________________________________ darwinbuild-dev mailing list darwinbuild-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/darwinbuild-dev
---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337