Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc

New issue 20098 by genggang1: Can't find "chrome.sln" file if following  
Chromium Build Instructions in Windows
http://code.google.com/p/chromium/issues/detail?id=20098

Chrome Version       : 23613
URLs (if applicable) :
Other browsers tested:
   Add OK or FAIL after other browsers where you have tested this issue:
      Safari 4:
   Firefox 3.x:
          IE 7:
          IE 8:

What is issue?
Can not find "chrome.sln" file if following Chromium Build
Instructions in Windows (http://dev.chromium.org/developers/how-tos/
build-instructions-windows).

My environment is:
1, WinXP
2, VS2005+VS 2005 Service Pack 1+ hotfix 935225 + hotfix 947315.
3, Windows 7 SDK.

The below is command line after I check out the source code, and no problem
is reported when this command line executed.

---------------bat-begin------------------------
:: @echo off
set MAIN_ROOT=E:\Chromium
set TRUNK_ROOT=E:\Chromium\trunk
set TOOL_ROOT=E:\Chromium\trunk\tools\depot_tools
set SRC_ROOT=E:\Chromium\trunk\src

cd %TRUNK_ROOT%

gclient config http://src.chromium.org/svn/trunk/src

:: Updating your checkout once by running gclient sync --force in the
source code directory.
gclient sync --force

:: If you don't want to sync, you need to generate the project files
with gclient runhooks --force.
gclient runhooks --verbose
---------------bat-end------------------------

What is expected?
After the upper steps, the "chrome.sln" should be generated or exist. But
there is no this file.


Please provide any additional information below. Attach a screenshot if
possible.


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to