mrowe at apple.com
Wed Nov 2 16:09:22 PDT 2011
On 2011-11-02, at 13:23, Adam Barth wrote:
> As discussed previously, I think it would benefit the project to move
> Previously, we've been unable to do this because of Apple's internal
> build process. In thinking about this problem again recently, I
> wonder if the following would work:
> Mark, do you have a sense for whether this plan is feasible? If not,
> is there another approach that would work better?
> (If my understanding is correct, we could also apply this approach to
> the other xcodeproj files, which would let us get rid of
> ForwardingHeaders and move Source/WebCore/platform to
There are a few related goals here that I'm aware of:
b) Separate WebCore/platform out of WebCore to help avoid layering violations.
c) Rework the Mac build process so that we can eliminate forwarding headers and remove the duplication of .xcconfig files.
The process for addressing a) and b) will be similar:
1) Move the relevant code from its current location to the new location.
2) Create a new Xcode project that builds the desired output in the appropriate fashion. Update other build systems as is applicable.
3) Apple starts including the new project in our build process.
I don't see any benefit or need to move existing Xcode projects as part of this process. Can you expand on why you included this in your proposal?
I'm not entirely clear on what we'll need to do to tackle c). My current feeling is that it will mainly involve reshuffling of Apple's build processes rather than any significant changes to WebKit.
More information about the webkit-dev