To get latest information, go here.
Below is the digest from current page of my Chromium page:
Download
This page provides a set of rpm packages to build your web browser from Chromium snapshot on CentOS 5.x, and also provides some pre-built binaries of the web browser. But pre-built browser binaries were just built for me. They are not new, and sometimes they may be useless...
To download binary rpms for x86: click here.
To download source rpms: click here.
(Currently there are no x86-64 binaries.)
NOTE: You can use rpm packages freely AT YOUR OWN RISK. Read here for the terms and condition of the Chromium browser.
Short instruction to run pre-built browser
Get following binary rpms: chromium-atk, chromium-cairo, chromium-expat, chromium-pango , chromium-glib2, chromium-gtk2, chromium-freetype, chromium-pixman , and chromium.
Install them into your CentOS system by “rpm -i” command. When you get some dependency errors, supply additional packages to fix them.
Choose “Chromium” on the gnome menu, Applications -> Internet, or run /usr/bin/chromium from a command line.
Short instruction to build your browser
Get all binary rpms except chromium, and get chromium source rpm.
Install them into your CentOS system by “rpm -i” command. When you get some dependency errors, supply additional packages to fix them also.
Don't forget to install chromium source rpm.Install more development packages for compilation. (ex. gcc44-g++) See here if you are uncertain. The list is not accurate for CentOS5, but useful. In this time, you don't need to install rpms that are already installed at 1st step with “chromium-” prefix. For example, you don't need to install gtk2-devel because chromium-gtk2-devel has been installed.
Get recent source tarball, chromium.xxxxxx.tgz and depot_tools.tgz, from here, and put them on /usr/src/redhat/SOURCES/.
cd /usr/src/redhat/SPECS. Edit “Source0” in chromium.spec with your downloaded tarball file name. And set %enable_network 0, because we have already gotten recent sources.
Run “rpmbuild -ba chromium.spec”.
If you fail to build Chromium, the reason may be one of two:(1) There are still rpm packages to be installed.
(2) The source code in the tarball is now broken.
If (2), you can try with “%enable_network 1” later. It will sync with newest code via network, and the bug may be fixed in the newest code. If (1), you must see error messages carefully, and google some keywords in the messages to find rpm package to install.
0 件のコメント:
コメントを投稿