Dopo di ciò ho avviato subito il tutto in locale e ho notato subito la sua immediatezza nell'apertura di pagine come www.myspace.com .....
Ecco un ScreenShot:
Ecco la procedura per configurare la macchina per lo sviluppo:
Build Instructions (Windows)
This page has detailed information on building Chromium on Windows, including tips for troubleshooting and for speeding up the build. Note: If you've never built Chromium on Windows, first read Getting Started. PrerequisitesBuild environment
Chromium checkout scriptsDownload the depot_tools_win.zip package, which contains our gclient, gcl, and svn tools. Add the depot_tools directory to your path:C:\>set PATH=C:\depot_tools;%PATH% The depot_tools package automatically updates itself every time gclient is run. See the depot_tools page if you want to disable this behavior. Getting the codeCreate a directory (with no spaces anywhere in the path name) to hold your source code. In this example we'll assume it's c:\trunk, but other names are fine.Before syncing the client, visit the Chromium Buildbot waterfall and make sure it says tree OPEN at the top. If you sync while the tree is closed, the code may not compile or link. Once you've verified that the tree is open, run the following commands (using your directory in place of c:\trunk): cd c:\trunkYou can expect this to take about an hour. gclient config only needs to be run once to set up your working directory. It creates a .gclient file in your source directory that identifies the corresponding structure to pull from the repository. gclient sync will create several subdirectories in your tip directory. To update your tree in the future, you only need to run gclient sync from that directory. More information about gclient is available from the gclient wiki. Building ChromiumOpen the chrome/chrome.sln solution file in Visual Studio and build the solution. This can take from 15 to 40 minutes.If you just want the Chromium browser, and none of the tests, you can speed up your build by right-clicking chrome_exe in the solution explorer and selecting Build. You may want to make sure this project is the Startup project (which will display as bold) by right-clicking it and selecting Set as Startup Project. This will make Chromium (as opposed to some random test) build and run when you press F5. Accelerating the buildIn decreasing order of speedup:
OptionalRebuild / CleanYou can use Rebuild and Clean on individual projects to rebuild them. However, because of the large number of files generated by the build system, avoid using Rebuild All or Clean All - these do not erase everything! Instead delete the entire output directory (chrome\Debug or chrome\Release). Build Chromium with JavaScriptCoreOur default solution file is chrome.sln which includes the V8 JavaScript engine. If you need to make a reference build of Chromium using JavaScriptCore, you should use the chrome_kjs.sln solution file. You will also need to setJS_ENGINE_TYPE=_kjs in your environment, then run Visual Studio (devenv) from that same command line. From the command line, type: C:\trunk\src\chrome> set JS_ENGINE_TYPE=_kjs C:\trunk\src\chrome> devenv chrome_kjs.sln If the devenv command isn't found, run the Visual Studio 2005 Command Prompt in your Start menu (by default, under Microsoft Visual Studio 2005 > Tools). This will set up the correct environment to run Visual Studio from the command line. In Cygwin, use the following command: $ JS_ENGINE_TYPE=_kjs devenv chrome_kjs.sln TroubleshootingBuild failures on VistaIf you build on Vista, watch out for security issues. Make sure that the folder where you checked out your files is writable for users and not only for admins. Compilation failuresSome common things to think about when you have weird compilation failures:
If it still doesn't work, repeating this process probably won't help. chrome_kjs.sln tempfile problemsIf, while building JavaScriptCore, you see errors like: 3>Error in tempfile() using /tmp/dftables-XXXXXXXX.in: Parent directory (/tmp/) is not writable ...it's because the Cygwin installation included in the Chromium source is having trouble mapping the NT ACL to POSIX permissions. This seems to happen when Chromium is checked out into a directory for which Cygwin can't figure out the permissions in the first place, possibly when the directory is created from within a Cygwin environment before running mkpasswd. Cygwin then imposes its own access control, which is incorrectly restrictive. As a workaround, do one of the following:
Only one of these solutions should be needed. Running ChromiumThe chrome.exe executable can be found at chrome/Debug/chrome.exe or chrome/Release/chrome.exe, depending on the selected build configuration.DebuggingBecause of Chromium's unique architecture, there are a number of special challenges associated with development. See Debugging Chromium for more information.ContributingOnce you're comfortable with building Chromium, read the Contributing Code page for information about writing code for Chromium and contributing it.PackagingIf you want to package your build into a zip file, do the following:cd /path/to/chrome ./tools/build/win/make_zip.sh Release my-chromium This will create my-chromium.zip. You can change Release to Debug if you want to zip up the debug build instead. TroubleshootingError message: This application has failed to start because the application configuration is incorrect or The system cannot execute the specified programInstall Microsoft Visual Studio 2005 Service Pack 1 (download). P.S.: Farò una traduzione dei passaggi!!! |
Nessun commento:
Posta un commento