<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>57037</bug_id>
          
          <creation_ts>2011-03-24 10:52:16 -0700</creation_ts>
          <short_desc>Ideally project generation would not have to happen at sync time.</short_desc>
          <delta_ts>2013-04-08 11:01:28 -0700</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>Tools / Tests</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>55018</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="David Levin">levin</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>372928</commentid>
    <comment_count>0</comment_count>
    <who name="David Levin">levin</who>
    <bug_when>2011-03-24 10:52:16 -0700</bug_when>
    <thetext>0. Ideally one could use widely used tools to sync and build webkit. (This requirement is simply about making things simple and reliable.)
1. I would like to be able to switch branches in git and be able to build.
2. I would not like my sync time to increase dramatically. (Based on various measurements, gyp generation may add between 5% to 40% overhead to a sync -- although the gyp generation time is consistent, the sync time varies)
3. I have a concern that having gyp generation happen on a developers machine after sync&apos;ing may not work due to a slightly different machine configuration or a badly tested change in the gyp generation tool, etc. 

Now there is a concern that one could do a gyp change and not check in the generated files but we could have a test that runs to verify that the checked in version matches the generated version.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>