On Sep 23, 2011, at 3:36 PM, Yanke (Yon) Hu wrote: > I only care about MiniBrowser project, right click it, choose Properties. > In Configuration Properties->C/C++->General->Additional Include Directories, > I add : \WebKitBuild\Release\include (header files)
This should not be necessary. MiniBrowser already knows how to look in this location. > In In Configuration Properties->Linker->General->Additional Library > Directories , I add the position of \Common Files\Apple\Apple Application This also should not be necessary, nor even helpful. "Additional Library Directories" tells VS where to find .lib files. But Common Files\Apple\Apple Application Support doesn't contain any .lib files. WebKitLibraries\win\lib contains .lib files, but MiniBrowser.vcproj should already know how to look there. > Then I rebuild only MiniBrowser, > > It shows some error message like: > > > 1>Deleting intermediate and output files for project 'MiniBrowser', > configuration 'Debug_All|Win32' > 1>Performing Pre-Build Event... > 1>cygwin warning: > 1> MS-DOS style path detected: \Debug_All\buildfailed > 1> Preferred POSIX equivalent is: /cygdrive/c/Debug_All/buildfailed > 1> CYGWIN environment variable option "nodosfilewarning" turns off this > warning. > 1> Consult the user's guide for more details about POSIX paths: > 1> http://cygwin.com/cygwin-ug-net/using.html#using-pathnames > 1>Project : error PRJ0002 : Error result 1 returned from > 'C:\Windows\SysWow64\cmd.exe'. This error message means some earlier project failed to build and left a file called "buildfailed" in your WebKitBuild directory. You can look at the contents of that file to figure out which project failed. By the way, you shouldn't build the Debug_All configuration. That's only useful for internal builds at Apple. You should use the Debug configuration instead. -Adam
_______________________________________________ webkit-help mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-help
