On Mon, Nov 19, 2012 at 12:37 PM, Tim Larson <[email protected]>wrote:
> > WebKit isn't designed to be a standard alone library that can be built > > on any system. By design, one has to create a "port" that supplies OS- > > specific bits and pieces in Source/WebCore/platform and Source/WebKit. > > If one of existing ports build on FreeBSD, then that's great but I'm > > not certain if any of them will. > > Ahhh. Poking through the directory structure, I begin to understand. Any > part of "standard" Webkit can be replaced in a platform-specific way, if > necessary or desired. > It's more than that. Without supplying code in Source/WebCore/platform & Source/WebKit, WebKit doesn't even build or function. > So there are platform subdirs in just about every section of the > hierarchy. How is conditional building for these cases handled, in general, > in build/make files? > Each port uses its own build system. Apple uses xcodebuild on Mac, Visual Studio on Windows (windows port), Chromium uses gyp, Qt uses cmake, and so forth. So some files are only listed in one port's build files while shared files are listed on all build files. For the shared code, we use PLATFORM(*) to #ifdef port-specific code. (See Source/WTF/wtf/Platform.h). - R. Niwa
_______________________________________________ webkit-help mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-help
