[darwinbuild] Greetings and a possible enhancement
Hi - I just discovered darwinbuild. After foolishly attempting to build CFNetwork on my own through simple trial and error. When I tried to use darwinbuild to build CFNetwork, I was impressed to see it following a dependency tree to install the required frameworks, tools, and headers. However, it was not quite accurate. It seems likely that if I were to build a few other projects first, I would "end up" with most of the stuff that was missing, but I assume ultimately you'd like to have accurate dependencies for everything. Is it appropriate for me to submit my observations here? Or does your dependency info come straight from Apple? For what it's worth, the missing stuff for building CFNetwork in a fresh darwinbuild 8G32 root: 1. The /usr/bin/cc link doesn't exist. It looks like "gcc_select" is what ultimately installs it. 2. mach-o/dyld.h doesn't exist. It looks like a header dependency on "libdyld" instead of "dyld" would fix this? 3. JavaScriptGlue framework needs to be installed for CFNetwork to build. Let me know if there's a more appropriate channel for communicating this information, or if such precision is a design goal or not. Thanks, Daniel
On Jan 23, 2006, at 7:31 AM, Daniel Jalkut wrote:
When I tried to use darwinbuild to build CFNetwork, I was impressed to see it following a dependency tree to install the required frameworks, tools, and headers. However, it was not quite accurate. It seems likely that if I were to build a few other projects first, I would "end up" with most of the stuff that was missing, but I assume ultimately you'd like to have accurate dependencies for everything.
Right.
Is it appropriate for me to submit my observations here? Or does your dependency info come straight from Apple?
Yes, this is the appropriate list. We maintain the dependency info as part of DarwinBuild.
For what it's worth, the missing stuff for building CFNetwork in a fresh darwinbuild 8G32 root:
1. The /usr/bin/cc link doesn't exist. It looks like "gcc_select" is what ultimately installs it.
2. mach-o/dyld.h doesn't exist. It looks like a header dependency on "libdyld" instead of "dyld" would fix this?
3. JavaScriptGlue framework needs to be installed for CFNetwork to build.
Let me know if there's a more appropriate channel for communicating this information, or if such precision is a design goal or not.
These recommendations look good. Thanks for the feedback! - Kevin
Glad to know that the feedback is helpful. And thanks for all the hard work you've put into this project. Daniel On Jan 24, 2006, at 6:06 PM, Kevin Van Vechten wrote:
On Jan 23, 2006, at 7:31 AM, Daniel Jalkut wrote:
When I tried to use darwinbuild to build CFNetwork, I was impressed to see it following a dependency tree to install the required frameworks, tools, and headers. However, it was not quite accurate. It seems likely that if I were to build a few other projects first, I would "end up" with most of the stuff that was missing, but I assume ultimately you'd like to have accurate dependencies for everything.
Right.
Is it appropriate for me to submit my observations here? Or does your dependency info come straight from Apple?
Yes, this is the appropriate list. We maintain the dependency info as part of DarwinBuild.
For what it's worth, the missing stuff for building CFNetwork in a fresh darwinbuild 8G32 root:
1. The /usr/bin/cc link doesn't exist. It looks like "gcc_select" is what ultimately installs it.
2. mach-o/dyld.h doesn't exist. It looks like a header dependency on "libdyld" instead of "dyld" would fix this?
3. JavaScriptGlue framework needs to be installed for CFNetwork to build.
Let me know if there's a more appropriate channel for communicating this information, or if such precision is a design goal or not.
These recommendations look good. Thanks for the feedback!
- Kevin
participants (2)
-
Daniel Jalkut
-
Kevin Van Vechten