[webkit-dev] Handling of feature dependencies

[Konstantin Tokarev]

Hi all,

What is the right way to handle dependencies between features set in time of configuration?

For example, I'd like to shrink some functionality ("feature B") in embedded browser, and therefore add
option --[no]-B flag to build-webkit, but it will break existing "feature A" if it is disabled

I can see several ways how to solve it:
* Automatically disable A in build-webkit if B is disabled
* Replace checks for ENABLE(A) in sources with ENABLE(A) && ENABLE(B)
* Let build fail if somebody disables B but enables A

What is the most correct way to handle this? 

-- 
Regards,
Konstantin