If you're secure in your understanding of depot_tools, cygwin, svn, you can
archive now.
I'm still a relative newbie, but I thought I knew what to do...

Still...I spent the better part of the day trying to get a correctly
building checkout of chromium on a new windows7 64bit box, and in the hopes
that I can save some other poor newbie the time, here's what I figured out
(this has probably all been covered before).
Cygwin svn was doing something horrible (probably permissions-related) to my
third_party/python_24 that caused the python binary not to run. The visible
symptom was that my build generated a ton of cryptic "Error 24"s from
Cmd.exe.

The solution was to use the windows svn binaries. The way I accomplished
this was to run depot_tools for the first time from a regular windows
command.exe so it installs win32 svn & python [also, I needed to set my path
so it depot_tools/svn appear first]. This fixed the svn checkout problem.

Lastly, I had trouble running gclient from a cygwin bash shell. If you are
using the windows binaries of svn & python, gclient has to run gclient.bat
so it sets paths correctly (otherwise python & svn get paths with
/cygdrive/... in them and give up). This will work correctly from a regular
cygwin bash terminal -- however, if you are using putty, it'll report your
TERM as "xterm" and the gclient script will call gclient.py and not set
paths correctly.

So, in summary -- for those who will soon be setting up shiny new machines
-- here's what worked for me (I'm sure other's have working setups as well):

1) Download depot_tools
2) Run gclient for the first time from command.exe (so you get the windows
binaries)
3) Put /cygdrive/path/to/depot_tools as the FIRST component of you cygwin
path (from .profile or .bashrc)
4) If your gclient spits out errors about /cygdrive/... paths, try running
gclient.bat directly (it's possible your TERM=="xterm").

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to