[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
I think what you're describing is a list of uses for the tar file. I think they are valid uses, but I would say thata) what you describe as problems with the build system are not "build system" problems, they're more "the tarball doesn't satisfy my usecase" problems. The tarball was not intended to be the build system. b) If you want a specific version of the code, gclient sync --revision src@ Really, the most basic goal of the tar file was that just before launch day, we were launching a huge open source project and I was looking at projected queries per second (QPS) to the SVN server and freaking out. As such, we put up the tarball to reduce the load. (Even with that, I think the SVN server prettymuch keeled over on launch day). We actually didn't even start doing updates to the tarball until recently (for quite a while it was still the initial version of the source code). What you're describing are other valid use cases, but given everything else we're trying to work on, and given that they can be satisfied by other (relatively simple) methods, I don't (personally) think it's worth trying to solve the issues you point out with the tarball. Certainly that wasn't the original intent for providing the tarball. my $0.02 On Wed, Feb 4, 2009 at 10:31 AM, noemata wrote: > > I had also assumed that the tar ball and SVN repository were > complete. Though I appreciate the arguments associated with the > manner in which the build process is implemented, ultimately it ends > up being self limiting. At present, there is no easy way to have > historical snapshots of working releases. This is a fairly common > practice that simplifies certain forms of regression testing. > > In our internal effort, I am the one dolling out a functional build of > Chromium by packaging a working archive file for others. The gclient > idea works, but it is fragile. It's much simpler to provide a fully > vetted build environment rather than rely on a tool that has to push > and pull it into place on a developer's system. > > Needing to accommodate different OS build targets is precisely why you > want to have OS specific tar archives. It's trivial to do. The only > reason I would choose not to do so is to obfuscate the build process, > thus keeping a certain class of software developer away from working > with Chromium. > > Running the test suite is even more fragile than building Chromium. > On my setup, most tests fail because it seems like the test > environment isn't configured correctly. I suspect this isn't > intended. Yet another self limiting characteristic of the present > build system. > > Surely, it's not that hard to have three sets of archives that provide > a complete snapshot of a working build environment. Internal to > Google, you must gen these anyways, so what's the issue? All such > archives should deliver a built version of Chromium to the recipient > so they can fire up the tests. I see this as the most basic goal of > the tar archive. Second to that is actually building it. > > On Feb 4, 3:13 am, Pam Greene wrote: > > We could make fully self-sufficient tarballs, but then we'd need three > > separate ones, since the three platforms have different dependencies. > (Or > > we'd need to stick Mac and Linux developers with downloading a bigger > > tarball than they need.) I think it's fair to require a sync after > > downloading the tarball, since you'll need to have the tools working at > some > > point. If you don't ever want to update your source code, you can use the > > "continuous" builds. > > > > (For the moment, since the tarballs are generated arbitrarily at 2 AM, > > syncing to a working build is a good idea anyway. But I plan to change > it > > to package up a known-green revision.) > > > > - Pam > > > > On Tue, Feb 3, 2009 at 9:57 PM, Nicolas Sylvain >wrote: > > > > > > > > > > > > > On Tue, Feb 3, 2009 at 9:55 PM, Brett Wilson > wrote: > > > > >> On Tue, Feb 3, 2009 at 9:05 PM, wrote: > > >> > What evan means is that after downloading the tar ball, you need to > run > > >> > gclient sync to get all the platform specific dependencies. > > > > >> > We recently started generating the source tar ball on a regular > basis > > >> and > > >> > it doesn't include all the Windows and Mac dependencies from the > > >> > src/third_party directory. Running gclient sync will download these > > >> > platform specific dependencies for you. > > > > >> In that case, the build instructions are out of date. I updated the > > >> getting-the-code page to reflect that this is now required. > > > > > If this is now required, we screwed up somewhere. The goal of the > tarball > > > is mainly to give an easy way for people to download and build > chromium. If > > > they need to call gclient sync, it defeats the purpose. > > > > > Are you sure we really need that? > > > > > Nicolas > > > > >> Brett- Hide quoted text - > > > > - Show quoted text - > > > --~--~-~--~~~---~--~--
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
I had a similar problem. I used an svn checkout. The entrire third_party/cygwin directory went missing in the tarball. Also, I suggest aria2c to download the tarball in the future which is better than the browser. On Feb 4, 10:33 am, Evan Martin wrote: > On Wed, Feb 4, 2009 at 10:31 AM, noemata wrote: > > Surely, it's not that hard to have three sets of archives that provide > > a complete snapshot of a working build environment. Internal to > > Google, you must gen these anyways, so what's the issue? All such > > archives should deliver a built version of Chromium to the recipient > > so they can fire up the tests. I see this as the most basic goal of > > the tar archive. Second to that is actually building it. > > I agree with all of your points but this one: part of the reason the > tarballs are so often wrong or out of date is that nobody within > Google uses them. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
On Wed, Feb 4, 2009 at 10:31 AM, noemata wrote: > Surely, it's not that hard to have three sets of archives that provide > a complete snapshot of a working build environment. Internal to > Google, you must gen these anyways, so what's the issue? All such > archives should deliver a built version of Chromium to the recipient > so they can fire up the tests. I see this as the most basic goal of > the tar archive. Second to that is actually building it. I agree with all of your points but this one: part of the reason the tarballs are so often wrong or out of date is that nobody within Google uses them. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
I had also assumed that the tar ball and SVN repository were complete. Though I appreciate the arguments associated with the manner in which the build process is implemented, ultimately it ends up being self limiting. At present, there is no easy way to have historical snapshots of working releases. This is a fairly common practice that simplifies certain forms of regression testing. In our internal effort, I am the one dolling out a functional build of Chromium by packaging a working archive file for others. The gclient idea works, but it is fragile. It's much simpler to provide a fully vetted build environment rather than rely on a tool that has to push and pull it into place on a developer's system. Needing to accommodate different OS build targets is precisely why you want to have OS specific tar archives. It's trivial to do. The only reason I would choose not to do so is to obfuscate the build process, thus keeping a certain class of software developer away from working with Chromium. Running the test suite is even more fragile than building Chromium. On my setup, most tests fail because it seems like the test environment isn't configured correctly. I suspect this isn't intended. Yet another self limiting characteristic of the present build system. Surely, it's not that hard to have three sets of archives that provide a complete snapshot of a working build environment. Internal to Google, you must gen these anyways, so what's the issue? All such archives should deliver a built version of Chromium to the recipient so they can fire up the tests. I see this as the most basic goal of the tar archive. Second to that is actually building it. On Feb 4, 3:13 am, Pam Greene wrote: > We could make fully self-sufficient tarballs, but then we'd need three > separate ones, since the three platforms have different dependencies. (Or > we'd need to stick Mac and Linux developers with downloading a bigger > tarball than they need.) I think it's fair to require a sync after > downloading the tarball, since you'll need to have the tools working at some > point. If you don't ever want to update your source code, you can use the > "continuous" builds. > > (For the moment, since the tarballs are generated arbitrarily at 2 AM, > syncing to a working build is a good idea anyway. But I plan to change it > to package up a known-green revision.) > > - Pam > > On Tue, Feb 3, 2009 at 9:57 PM, Nicolas Sylvain wrote: > > > > > > > On Tue, Feb 3, 2009 at 9:55 PM, Brett Wilson wrote: > > >> On Tue, Feb 3, 2009 at 9:05 PM, wrote: > >> > What evan means is that after downloading the tar ball, you need to run > >> > gclient sync to get all the platform specific dependencies. > > >> > We recently started generating the source tar ball on a regular basis > >> and > >> > it doesn't include all the Windows and Mac dependencies from the > >> > src/third_party directory. Running gclient sync will download these > >> > platform specific dependencies for you. > > >> In that case, the build instructions are out of date. I updated the > >> getting-the-code page to reflect that this is now required. > > > If this is now required, we screwed up somewhere. The goal of the tarball > > is mainly to give an easy way for people to download and build chromium. If > > they need to call gclient sync, it defeats the purpose. > > > Are you sure we really need that? > > > Nicolas > > >> Brett- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
We could make fully self-sufficient tarballs, but then we'd need three separate ones, since the three platforms have different dependencies. (Or we'd need to stick Mac and Linux developers with downloading a bigger tarball than they need.) I think it's fair to require a sync after downloading the tarball, since you'll need to have the tools working at some point. If you don't ever want to update your source code, you can use the "continuous" builds. (For the moment, since the tarballs are generated arbitrarily at 2 AM, syncing to a working build is a good idea anyway. But I plan to change it to package up a known-green revision.) - Pam On Tue, Feb 3, 2009 at 9:57 PM, Nicolas Sylvain wrote: > > > On Tue, Feb 3, 2009 at 9:55 PM, Brett Wilson wrote: > >> >> On Tue, Feb 3, 2009 at 9:05 PM, wrote: >> > What evan means is that after downloading the tar ball, you need to run >> > gclient sync to get all the platform specific dependencies. >> > >> > We recently started generating the source tar ball on a regular basis >> and >> > it doesn't include all the Windows and Mac dependencies from the >> > src/third_party directory. Running gclient sync will download these >> > platform specific dependencies for you. >> >> In that case, the build instructions are out of date. I updated the >> getting-the-code page to reflect that this is now required. > > > If this is now required, we screwed up somewhere. The goal of the tarball > is mainly to give an easy way for people to download and build chromium. If > they need to call gclient sync, it defeats the purpose. > > Are you sure we really need that? > > Nicolas > > >> >> >> Brett >> >> >> > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
I thought the point of the tarball was to bootstrap the process, not to remove the gclient dependencies. Doing a full checkout via gclient can be slow (lots of requests for lots of files) and taxing on our server (same reason). Having some base from which to start speeds it up and reduces load on the server. I don't think we ever had a hard requirement that the tarball be everything one would ever need, it just happened that the first versions did happen to be so. -Ian On Tue, Feb 3, 2009 at 9:57 PM, Nicolas Sylvain wrote: > > > On Tue, Feb 3, 2009 at 9:55 PM, Brett Wilson wrote: > >> >> On Tue, Feb 3, 2009 at 9:05 PM, wrote: >> > What evan means is that after downloading the tar ball, you need to run >> > gclient sync to get all the platform specific dependencies. >> > >> > We recently started generating the source tar ball on a regular basis >> and >> > it doesn't include all the Windows and Mac dependencies from the >> > src/third_party directory. Running gclient sync will download these >> > platform specific dependencies for you. >> >> In that case, the build instructions are out of date. I updated the >> getting-the-code page to reflect that this is now required. > > > If this is now required, we screwed up somewhere. The goal of the tarball > is mainly to give an easy way for people to download and build chromium. If > they need to call gclient sync, it defeats the purpose. > > Are you sure we really need that? > > Nicolas > > >> >> >> Brett >> >> >> > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
On Tue, Feb 3, 2009 at 9:55 PM, Brett Wilson wrote: > > On Tue, Feb 3, 2009 at 9:05 PM, wrote: > > What evan means is that after downloading the tar ball, you need to run > > gclient sync to get all the platform specific dependencies. > > > > We recently started generating the source tar ball on a regular basis and > > it doesn't include all the Windows and Mac dependencies from the > > src/third_party directory. Running gclient sync will download these > > platform specific dependencies for you. > > In that case, the build instructions are out of date. I updated the > getting-the-code page to reflect that this is now required. If this is now required, we screwed up somewhere. The goal of the tarball is mainly to give an easy way for people to download and build chromium. If they need to call gclient sync, it defeats the purpose. Are you sure we really need that? Nicolas > > > Brett > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
On Tue, Feb 3, 2009 at 9:05 PM, wrote: > What evan means is that after downloading the tar ball, you need to run > gclient sync to get all the platform specific dependencies. > > We recently started generating the source tar ball on a regular basis and > it doesn't include all the Windows and Mac dependencies from the > src/third_party directory. Running gclient sync will download these > platform specific dependencies for you. In that case, the build instructions are out of date. I updated the getting-the-code page to reflect that this is now required. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
What evan means is that after downloading the tar ball, you need to run gclient sync to get all the platform specific dependencies. We recently started generating the source tar ball on a regular basis and it doesn't include all the Windows and Mac dependencies from the src/third_party directory. Running gclient sync will download these platform specific dependencies for you. On Tue, 3 Feb 2009, DeArto20 wrote: > > I have not checked out the code using 'gclient sync'. Anyway, > > The URL for the build instructions I followed. > - 1. http://dev.chromium.org/developers/how-tos/build-instructions-windows > Link to here -> 2. > http://dev.chromium.org/developers/how-tos/get-the-code > Link to here -> 3. > http://build.chromium.org/buildbot/archives/chromium_tarball.html > > And it started to download chromium.r9045.tar.gz automatically. > --- > > I visited the server (http://src.chromium.org/viewvc/chrome/trunk/ > src/...) and looked over the latest version (directory revision 9125) > of the grit_resource_file.bat and third_party folder. > > And I verified that there are no differences between them (the latest) > and my local files. > - There are not python_24 and cygwin under third_party folder and > grit_resource_file.bat still references them. > > > So, in this case, if I check out the latest files using 'gclient > sync', is there anything that is changed? > > > On 2¿ù4ÀÏ, ¿ÀÀü11½Ã12ºÐ, Evan Martin wrote: > > You must use gclient sync to check out. What is the URL for the build > > instructions were you following? I can fix them. > > > > On Tue, Feb 3, 2009 at 6:04 PM, DeArto20 wrote: > > > > > I have downloaded r9040 tar-ball from the chromium web site and built > > > it in VS2005 > > > (Before building it, I have removed the previous version completely in > > > my hard disk.) > > > > > But it made lots of errors. - One of those was > > > 'generated_resources.h'. > > > > > So, I have looked into it in detail and found that the batch file > > > 'grit_resource_file.bat' is a little weird. > > > It has following lines in it. > > > > > --- > > > > > > --- > > > --- > > > :: Put cygwin in the path > > > call %SolutionDir%\..\third_party\cygwin\setup_env.bat > > > > > %SolutionDir%\..\third_party\python_24\python.exe %SolutionDir%\.. > > > \tools\grit\grit.py -i %InFile% build -o %OutDir% > > > --- > > > > > > --- > > > --- > > > > > It contains 'third_party\cygwin' and 'third_party\python_24'. But as > > > far as I know, those are not available anymore. > > > (r9040 doesn't have 'cygwin' or 'python_24' inside the 'third_party' > > > folder.) > > > > > How do you think about this? And what should I do for building the > > > project successfully? > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
I have not checked out the code using 'gclient sync'. Anyway, The URL for the build instructions I followed. - 1. http://dev.chromium.org/developers/how-tos/build-instructions-windows Link to here -> 2. http://dev.chromium.org/developers/how-tos/get-the-code Link to here -> 3. http://build.chromium.org/buildbot/archives/chromium_tarball.html And it started to download chromium.r9045.tar.gz automatically. --- I visited the server (http://src.chromium.org/viewvc/chrome/trunk/ src/...) and looked over the latest version (directory revision 9125) of the grit_resource_file.bat and third_party folder. And I verified that there are no differences between them (the latest) and my local files. - There are not python_24 and cygwin under third_party folder and grit_resource_file.bat still references them. So, in this case, if I check out the latest files using 'gclient sync', is there anything that is changed? On 2월4일, 오전11시12분, Evan Martin wrote: > You must use gclient sync to check out. What is the URL for the build > instructions were you following? I can fix them. > > On Tue, Feb 3, 2009 at 6:04 PM, DeArto20 wrote: > > > I have downloaded r9040 tar-ball from the chromium web site and built > > it in VS2005 > > (Before building it, I have removed the previous version completely in > > my hard disk.) > > > But it made lots of errors. - One of those was > > 'generated_resources.h'. > > > So, I have looked into it in detail and found that the batch file > > 'grit_resource_file.bat' is a little weird. > > It has following lines in it. > > > --- > > --- > > --- > > :: Put cygwin in the path > > call %SolutionDir%\..\third_party\cygwin\setup_env.bat > > > %SolutionDir%\..\third_party\python_24\python.exe %SolutionDir%\.. > > \tools\grit\grit.py -i %InFile% build -o %OutDir% > > --- > > --- > > --- > > > It contains 'third_party\cygwin' and 'third_party\python_24'. But as > > far as I know, those are not available anymore. > > (r9040 doesn't have 'cygwin' or 'python_24' inside the 'third_party' > > folder.) > > > How do you think about this? And what should I do for building the > > project successfully? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: build problem (chromium.r9040.tar.gz)
You must use gclient sync to check out. What is the URL for the build instructions were you following? I can fix them. On Tue, Feb 3, 2009 at 6:04 PM, DeArto20 wrote: > > I have downloaded r9040 tar-ball from the chromium web site and built > it in VS2005 > (Before building it, I have removed the previous version completely in > my hard disk.) > > But it made lots of errors. - One of those was > 'generated_resources.h'. > > So, I have looked into it in detail and found that the batch file > 'grit_resource_file.bat' is a little weird. > It has following lines in it. > > - > :: Put cygwin in the path > call %SolutionDir%\..\third_party\cygwin\setup_env.bat > > %SolutionDir%\..\third_party\python_24\python.exe %SolutionDir%\.. > \tools\grit\grit.py -i %InFile% build -o %OutDir% > - > > It contains 'third_party\cygwin' and 'third_party\python_24'. But as > far as I know, those are not available anymore. > (r9040 doesn't have 'cygwin' or 'python_24' inside the 'third_party' > folder.) > > > How do you think about this? And what should I do for building the > project successfully? > > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
