Chromium build instructions (Linux version) this page describes if compiled on the Linux operating system build Chromium browser.
If you want to test or chromium chromium to other platforms, porting, you continue reading. Small Tip: there is no Linux running Chromium Chromium browser, although some child module in linux compiled and a small part of the unit test passes, all those are just a command "implemented" alltestspass. prerequisites Note: our idea is that you can in any applicable in modern Linux distributions, and compile build Chromium we try to do our best to list the system build prerequisites. Of course, you can put up with Linux porting only at the beginning of this reality, and we are in the majority of Linux release testing is limited in Chromium, our development platform is Ubuntu8 (hardyheron) of a variety, we want you to be in this system there is a good luck. Linux platform requires the following software to compile build: Subversion > = 1.4 (Tip: If you are using the tarball (compressed format), it is difficult to focus on code changes, you need version 1.5 after we will fix it) (translator: Subversion is a version of than CVS advanced control software) pkg-config > = 0.20 (translator: pkg-config is a development library configuration tool) Python > = 2.4 (translator: Python programming language, in this case, Python environment, tools) Perl > 5.xgcc/g ++ > = 4.2bison > = 2.3 (translator: GNUbison syntax analysis conversion tools?) Flex > = 2.5.34gperf > = 3.0.3libnss3-dev > = 3.12 Ubuntu8 system, you can use the following command once all of the software: $ sudoapt-getinstallsubversionpkg-configpythonperlg ++ bisonflexgperflibnss3-dev gets code 1. Select the compile directory we will in this document that this directory is the variable $ CHROMIUM_ROOT.2. access code library Tools-$ cd $ CHROMIUM_ROOT $ svncohttp://src.chromium.org/svn/trunk/depot_tools/linuxdepot_tools (or download .tar.gz format compressed package files: depot_tools_linux.tar.gz) in order to maintain this compilation instructions of the integrity of the document, we assume that your depot_tools directory in your build directory ($ CHROMIUM_ROOT), but it is not necessary in this way, you can place it anywhere, and in your PATH environment variable, or other variables in the path, 3. because many people on this highly interesting results in our temporary work server cannot access, please try to download the code from SVN snapshots, unzip it and follow the instructions in the upgrade code, you will work through gclient synchronization get the same results-$ cd $ CHROMIUM_ROO $ exportLANG = C # tempworkaroundforgclientbehavior $./depot_tools/gclientconfighttp://src.chromium.org/svn/trunk/src $./depot_tools/gclientsync Tip: default, run gclient sync tool, depot_tools will automatically update the code to the latest version (ready), if you want to turn off this behavior, check the contents of the document page depot_tools. build compiled build current Chromiumlinux subset: $ cd $ CHROMIUM_ROOT/src/chrome $ .. /Third_party/scons/scons.pyHammer in compiled, executable is placed in $ CHROMIUM_ROOT/src/chrome/Hammer Directory problem handling sh: d: notfoundwhileprocessingHammer/webkit/WebCore/xml/XPathGrammar.y you didn't install bison, we are repairing our build scripts to use it more easy to use and friendly, but when you read this document, we alter the code hasn't been updated in a record!
No comments:
Post a Comment