[webkit-dev] Question regarding build flags for the features

Eli Fidler efidler at rim.com
Wed Mar 24 08:20:16 PDT 2010

I just happened to compile this list yesterday. I'll update the wiki
page. People should fill in the information about what their setting do,
especially for the ports.


-----Original Message-----
From: webkit-dev-bounces at lists.webkit.org
[mailto:webkit-dev-bounces at lists.webkit.org] On Behalf Of Maciej
Sent: Tuesday, March 23, 2010 8:35 PM
To: Dmitry Titov
Cc: WebKit-Dev Development
Subject: Re: [webkit-dev] Question regarding build flags for the

On Mar 23, 2010, at 1:22 PM, Dmitry Titov wrote:

> If we had a single flag for all those (ENABLE_FILE_API ?) then a  
> port would have to implement all features at once to be able to  
> enable it. It might be inconvenient. If the code is not shared and  
> those flags can be enabled in any combination, why not keep them  
> separate?
> On a related note, it'd be nice to have a page (on a wiki?) with a  
> list of those flags with some sort of a status/owner, and possibly  
> some info on what a port should implement to be able to enable a  
> feature.

Shipping Safari has a very limited form of the File API, so I'd prefer  
a plan where we do not regress the already shipped capability. That  
could mean either multiple flags for different subfeatures, or making  
sure to implement back ends for the mac and win ports when landing any  
new features. Maintainers of other ports may have similar concerns,  
but I cannot say offhand what has already shipped in other ports.

Incidentally, some but not all porting macros are defined here:
 >. The first part of the page is hypothetical (i.e. a plan for  
revising some of the macros) but if anyone would like to help document  
macros in use at the end, that would be great.


webkit-dev mailing list
webkit-dev at lists.webkit.org

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

More information about the webkit-dev mailing list