Summary: | Add --minimal option to webkit-build | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Jakob Petsovits <jpetsovits> | ||||||||
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> | ||||||||
Status: | RESOLVED FIXED | ||||||||||
Severity: | Normal | CC: | manyoso | ||||||||
Priority: | P2 | ||||||||||
Version: | 528+ (Nightly build) | ||||||||||
Hardware: | PC | ||||||||||
OS: | All | ||||||||||
Attachments: |
|
Description
Jakob Petsovits
2009-07-30 12:45:46 PDT
Created attachment 33807 [details]
Add --minimal option to webkit-build
Created attachment 33808 [details]
Add --minimal option to webkit-build (try 2)
New version, this one gets the --minimal option out of @ARGV and thus makes it work with subsequent code that makes use of @ARGV still, like Qt's qmake stuff.
Created attachment 33812 [details]
Add --minimal option to webkit-build (try 3)
Fix for a spelling issue, pointed out by Adam Treat: explicitely -> explicitly.
Comment on attachment 33812 [details]
Add --minimal option to webkit-build (try 3)
I think it would be better and clearer for --minimal to be parsed like all the other options. After the GetOptions call, if $minimal is true you can just loop over @features and set all the values that don't match the default to 0.
Comment on attachment 33812 [details]
Add --minimal option to webkit-build (try 3)
Jakob convinced me that my suggested approach is not better.
r=me
|