Perhaps someone should set up a "random" bot that will select uniformly at random from the set of *all* supported configurations. If a configuration is known to be unsupported, or is found to be so buggy that it is untenable, the configuration should be removed from the documentation. After all, the point of having all these build switches is so that the user (me) can customize the build. If the switches aren't tested, then they don't work; and if they don't work, there's no point in having them.
If I just want to build the core of WebKit2 (omitting optional components where possible), what *is* the recommended approach? Obviously --minimal is a bad idea right now. Also, should I continue passing --debug? It seemed like some of the errors went away without --debug. -Arthur On Mon, Jun 25, 2012 at 12:56 PM, Eric Seidel <[email protected]> wrote: > If someone wanted to set up a --minimal bot, I'm sure that would be > welcome. We used to have a --qt --minimal bot at some point. > > http://trac.webkit.org/wiki/BuildBot > >> On Mon, 25 Jun 2012 12:03:12 -0700, Arthur O'Dwyer <[email protected]> wrote: >>> >>> I'm trying to build WebKit by the simplest possible method. I checked >>> out the SVN tree and did "cd WebKit ; Tools/Scripts/build-webkit >>> --debug --minimal". This produced compiler errors! >> >> I tried the same thing a while ago, and submitted patches to fix some of the >> issues, but what i was told is that there aren't really any bots building >> with --minimal, so it's not guaranteed to build. >> >> Last i remember, after you fix those issues you mention you're probably >> gonna come up against trickier ones in --web-audio, --geolocation, >> --netscape-plugin-api and --fullscreen-api [...] _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
