My SDK install directory is incorrect (should be v6.0 instead of v6.1) so I tried to edit the config.cmd file to represent that. However, I keep getting an error that the config.cmd file is corrupt after I edit and save it. I'm assuming it's the config.cmd chksum that's causing the error and I also see that there is a way to disable the chksum in the config.cmd file. What do I need to do to disable the chksum feature?
Thanks, On Oct 30, 4:20 pm, SkyLined <[EMAIL PROTECTED]> wrote: > Hi all, > > Because I needed ToT builds of Chrome on multiple machines and because > I like automation, I created a script that can automatically get you > set up to build Chrome. The aim of this project is to require only one > manual download to get set up. It is pretty much feature complete and > I need some people to test this and comment on it. Here's what it > does: > > - check if your machine meets the requirements for building Chrome > from source (VS2005 and Windows SDK installed) > - download and unpack depot tools > - download and unpack source tarball > - sync Chromium source > - build Debug/Release Google Chrome > - clean the build environment and fix a number of issues. > - detect known build errors and provide useful tips to solve them. > > (Basically everything > onhttp://dev.chromium.org/developers/how-tos/getting-started, > with a few added features.) > > I am looking for people that are willing to give it a try and give > feedback. > > WARNING: This script is in development and may not function properly > which could potentially cause damage to your system, which will be > your problem (but I sure hope it does not). It's not officially > supported in any way, so if you have a problem, I cannot guarantee you > will receive help in fixing it. > WARNING: The script downloads scripts and executables over HTTP > connections and executes them. As with any such download, there is > always a risk of an attacker modifying the executables in transit and > taking over your system when they are executed. (Though I highly doubt > it) > > Now that we have that out of the way, here's how to get started: > 1) Downloadhttp://skypher.com/SkyLined/download/get_chromium/get_chromium.cmd > 2) Run it. > It will ask you a few questions about where you want your source > installed and such and then automatically download and unpack > everything. This includes downloading md5sum.exe and 7za.exe for > checking downloads and unpacking them. If automatic downloading and/or > unpacking fails, it should fall back to asking you to do it manually > before it continues with the installation. Once everything is > installed, it will sync source and build Debug Google Chrome. > > PS. It has a crude automatic update system that checks if there is a > new version every time you run it. That way, you can benefit from bug > fixes and updates. This is specifically helpful for the known build > errors problem solving feature; when there is a known issue, I can > update this and everybody that encounters it will be alerted to the > potential fix. > > Cheers, > > SkyLined --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
