Bug 79168

Summary: Tools\MiniBrowser return error 1 from C:\Windows\SysWow64\cmd.exe
Product: WebKit Reporter: Leslie Zhai <zhaixiang>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: mrahaman
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows 7   

Leslie Zhai
Reported 2012-02-21 17:19:12 PST
I built WebKit-r108038\Tools\MiniBrowser under Windows 7 64-bit with Visual Studio 2005, it return error 1 from C:\Windows\SysWow64\cmd.exe I downloaded WebKit nightly r108038 binary for Windows and source including Tools directory.
Attachments
Mustafizur Rahaman( :rahaman)
Comment 1 2012-02-22 21:54:02 PST
(In reply to comment #0) > I built WebKit-r108038\Tools\MiniBrowser under Windows 7 64-bit with Visual Studio 2005, it return error 1 from C:\Windows\SysWow64\cmd.exe Could you please provide more specific details as when you got the error? Did you follow the build steps exactly as it is being mentioned? > > I downloaded WebKit nightly r108038 binary for Windows and source including Tools directory.
Leslie Zhai
Comment 2 2012-02-22 22:15:53 PST
(In reply to comment #1) > (In reply to comment #0) > > I built WebKit-r108038\Tools\MiniBrowser under Windows 7 64-bit with Visual Studio 2005, it return error 1 from C:\Windows\SysWow64\cmd.exe > Could you please provide more specific details as when you got the error? Did you follow the build steps exactly as it is being mentioned? I build the Source under Gentoo Linux before successfully, but did not experienced it under Windows. I simply emerged the binary and source under WebKit-rxxx folder, then directly build the MiniBrowser without building the WebKit because I hold the view that there is binary for Windows already. And right now I followed the http://blog.ashodnakashian.com/2012/01/building-webkit-on-windows-7-with-vs2010 to rebuild WebKit under Windows 7 64-bit with VS2010 > > > > I downloaded WebKit nightly r108038 binary for Windows and source including Tools directory.
Note You need to log in before you can comment on or make changes to this bug.