Package Search
 
Members: 351 | Topics: 766 | Posts: 3210
We welcome our newest member: Somewhat Reticent
Info
» You aren't logged in, login or registerOnline: No members and 3 guests | Time: 10:52
Google Chromium
paldo Support Forum    Upkg    General Discussion
Reply Reply   Subscribe Topic Subscribe Topic
11 posts found.Page: 1 2
 Google Chromium
Junior Mitglied
 
 
dustin.winski5
 
Posts: 4
Registered: 2010-04-27
Hey, I'm trying to install Google chromium on my laptop could anyone help me? All I need is the steps to build it from source, or is it in the repositories?
Profile   Private Message   E-Mail
Created: 2010-05-06 18:19
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Senior Mitglied
 
 
 
Posts: 216
Registered: 2008-07-04
We don't have chromium on paldo's repository.

The best way for building it is making a package on a local repository and using upkg to build it.

To know what to do there is a wikipage from chromium page that explains the process of building... I'll take a look and then see if I can make a step-by-step for how to build it on paldo.
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez
Profile   Private Message   E-Mail
Created: 2010-05-06 22:26
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Senior Mitglied
 
 
 
Posts: 216
Registered: 2008-07-04
Please use http://www.paldo.org/wiki/HowtoBuildPackage to set your local repository if you don't have one.

After that add a package called chromium

Here is the xml Spec - put it on $REPO/spec with the name as chromium.xml

Code[In neuem Fenster öffnen]
<?xml version="1.0"?>
<package name="chromium">
<description>Chromium is the open-source project behind Google Chrome</description>
<releases>
<release version="r46552" revision="1" branch="stable">
<deps>
<dep name="Python" />
<dep name="perl" />
<dep name="nss" />
<dep name="alsa-lib" />
<dep name="gconf-2.0" />
<dep name="glib-2.0" />
<dep name="gtk+-2.0" />
<dep name="nspr" />
<dep name="freetype" />
<dep name="cairo" />
<dep name="bzip2" />
<dep name="jpeg" />
<dep name="expat" />
<dep name="mesa" />
</deps>
<build>
<script>
<archive name="chromium.$VERSION" type="tgz">
<cmd>make -j 2 BUILDTYPE=Release PREFIX=/usr chrome chrome_sandbox</cmd>
<cmd>make install</cmd>
</archive>
</script>
</build>
</release>
</releases>
</package>


Now download the tgz file and put it into $REPO/sources/chromium/ with the name chromium.r46552.tgz . Remember the source code of chromium is 722 mB (it's huge)

EDIT: Forgot to say where to get the source : http://build.chromium.org/buildbot/archives/chromium_tarball.html

Now you can build it using upkg with the command:

upkg-build --verbose chromium

Upkg will install the dependencies and then try to build it

Remember that I haven't tested any of it so it might be a very unstable package, it might not compile or not install... it might be a useless installation.

Compiling google chromium is really not easy, if you do prefer it over firefox, epiphany, midori, or opera which are on our repositories, then feel free to try to build it.
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez
Profile   Private Message   E-Mail
Created: 2010-05-06 23:50 | Modified: 2010-05-06 23:51 by diogo
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Junior Mitglied
 
 
dustin.winski5
 
Posts: 4
Registered: 2010-04-27
Thanks, I do appreciate your reply, I'll do it that way.
Profile   Private Message   E-Mail
Created: 2010-05-07 05:19
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Senior Mitglied
 
 
 
Posts: 216
Registered: 2008-07-04
Hi everyone,

So as I stated before compiling and installing chromium is a hard thing to do, the chromium developers have not created a simple ./configure make make install, so things need to be nested so we get it really configured and well thought, the simple instructions I gave before doesn't do a good job, so I've been dealing on translating the gentoo ebuild and arch's pkgbuild so we get a good chromium xml spec.

I'll be testing it right now and if all goes well I'll post here the final spec (it is already a 104 lines for 1 testing release instructions :P )

All in all, I think I finally got a complete chromium xml spec, but I'll test it first.
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez
Profile   Private Message   E-Mail
Created: 2010-07-22 19:24
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Mitglied
 
 
 
Posts: 73
Registered: 2009-07-15
Great to know Diogo!!!
Chromium rocks! I'v seen it as a perfect match for lxde distros, and it would also be for Paldo, due to both being fast and light.
So, good work and thanks.
Profile   Private Message
Created: 2010-07-22 20:10
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Senior Mitglied
 
 
 
Posts: 216
Registered: 2008-07-04
So,

Building chromium takes a long, long, really long time (just as long as building gcc).

I had to dig and fix 3 things:

It is always better for distributions to have their programs using shared libraries instead of static ones, but chromium team seem to adopt the static approach so that they can assure that the libraries used are always the same and consistent. But mainly this is not a good approach as if the system gets and ffmpeg bug-fix upgrade the chromium will not get it as it uses a bundled one.

So I decided to make all the libraries shared, but apparently 3 of them can't be shared here are the reasons:

1) ffmpeg : ffmpeg 0.5.1 is not complete yet and the little part that is missing (that no one seem to use) is a part that chromium requires, so until ffmpeg releases a new version we need to keep chromium using static/bundled ffmpeg (it seems that the development snapshots already include this part, but it doesn't make sense to request an upgrade to a possibly unstable version so that chromium can work with shared ffmepg).

2) openssl: chromium doesn't compile with the shared openssl (still don't know why) so it needs to use the bundled library.

3) libevent: chromium needs libevent bigger then 1.4.13 and paldo still uses 1.3.x, so for now using a bundled library as well.

After fixing these 3 cases the package compiled fine, the problem is that it failed on the installation, which I'm checking right now, but again it will take a long time to compile it again to see if the installation will proceed easily now.

UPDATE:: doing final tests for stability check and fixing installation of basic launcher script, the compilation on my system (core2duo 2GHz + 2 GB Ram) takes the total of 38 minutes of compilation.
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez
Profile   Private Message   E-Mail
Created: 2010-07-23 01:04 | Modified: 2010-07-23 02:00 by diogo
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Senior Mitglied
 
 
 
Posts: 216
Registered: 2008-07-04
Hi everyone,

So finally I got it nailed, here I'm posting the spec for chromium 6 for paldo

It takes a long time to build, but it works fine (I'm posting from chromium on paldo right now).

You'll need to download the source code from http://build.chromium.org/buildbot/official/chromium-6.0.473.0.tar.bz2

The spec is based on gentoo ebuild, with some extra things from arch pkgbuild. the commented parts are instructions for when ffmpeg, libevent and openssl get upgrade so that they come to be compatible as explained on the earlier post.

Code[In neuem Fenster öffnen]
<?xml version="1.0"?>
<package name="chromium">
<!-- source-code: http://build.chromium.org/buildbot/official/ -->
<description>An open-source browser project to help move the web forward</description>
<releases>
<release version="6.0.473.0" revision="1" branch="testing">
<settings>
<variable name="CHROMIUM_HOME">/usr/lib/chromium-browser</variable>
</settings>
<deps>
<dep name="bzip2" />
<!-- using bundled until upgrade to version >=1.4.13 -->
<!--dep name="libevent" /-->
<dep name="nss" />
<dep name="gconf-2.0" />
<dep name="gnome-keyring" />
<dep name="alsa-lib" />
<dep name="jpeg" />
<dep name="libpng" />
<!-- using bundled until upgrade to version > 0.5.1 -->
<!--dep name="ffmpeg" /-->
<dep name="cups" />
<dep name="zlib" />
<dep name="gtk+-2.0" />
<dep name="xscrnsaver" />
<dep name="perl" />
<dep name="gperf" />
<dep name="pkgconfig" />
<dep name="flex" />
<dep name="gnome-icon-theme" />
<dep name="hicolor-icon-theme" />
<dep name="xdg-utils" />
<dep name="yasm" />
<dep name="libxml2" />
<dep name="libxslt" />
<!-- using bundled until compilation problem gets fixed -->
<!--dep name="openssl" /-->
</deps>
<build>
<script>
<archive name="chromium-$VERSION">
<!-- We can't use system ffmpeg , version 0.5.1 is incompatible -->
<!-- System libevent don't work it need to be bigger then 1.4.13 -->
<!-- Can't compile with system openssl -->
<cmd>build/gyp_chromium -f make build/all.gyp --depth=. -Duse_system_bzip2=1 -Duse_system_ffmpeg=0 -Duse_system_libevent=0 -Duse_system_libjpeg=1 -Duse_system_libpng=1 -Duse_system_zlib=1 -Duse_system_ssl=0 -Duse_system_yasm=1 -Duse_system_libxml=1 -Duse_system_libxslt=1 -Dproprietary_codecs=1 -Duse_cups=1 -Dv8_use_snapshot=0 -Denable_gpu=0 -Dlinux_use_tcmalloc=0 -Dno_strict_aliasing=1 -Dgcc_version=44 -Dwerror= -Dlinux_sandbox_path=$CHROMIUM_HOME/chrome_sandbox -Dlinux_sandbox_chrome_path=$CHROMIUM_HOME/chrome</cmd>
<cmd>make -j 2 chrome chrome_sandbox BUILDTYPE=Release</cmd>
<!-- Install by hand as chromium doesn't provide an easy way -->
<cmd>[ -d $CHROMIUM_HOME ] || mkdir -p $CHROMIUM_HOME</cmd>
<cmd>install -m0755 out/Release/chrome $CHROMIUM_HOME</cmd>
<cmd>install -m4755 out/Release/chrome_sandbox $CHROMIUM_HOME</cmd>
<cmd>install -m0755 out/Release/xdg-settings $CHROMIUM_HOME</cmd>
<text dest="$CHROMIUM_HOME/chromium-launcher.sh" mode="0755">
#!/bin/sh
#
# Copyright (c) 2009 The Chromium Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.

if ! grep -q /dev/shm /proc/mounts ; then
echo "You don't have tmpfs mounted at /dev/shm.\
The browser isn't going to work in that configuration.\
Please uncomment the /dev/shm entry in /etc/fstab,\
run 'mount /dev/shm' and try again."
exit 1
fi

if [ `stat -c %a /dev/shm` -ne 1777 ]; then
echo "/dev/shm does not have correct permissions.\
The browser isn't going to work in that configuration.\
Please run chmod 1777 /dev/shm and try again."
exit 1
fi

# Let the wrapped binary know that it has been run through the wrapper
export CHROME_WRAPPER="`readlink -f "$0"`"

PROGDIR="`dirname "$CHROME_WRAPPER"`"

case ":$PATH:" in
*:$PROGDIR:*)
# $PATH already contains $PROGDIR
;;
*)
# Append $PROGDIR to $PATH
export PATH="$PATH:$PROGDIR"
;;
esac

# Set the .desktop file name
export CHROME_DESKTOP="chromium-chromium.desktop"

exec "$PROGDIR/chrome" "$@"
</text>
<cmd>install -m0644 out/Release/chrome.pak $CHROMIUM_HOME</cmd>
<cmd>install -m0644 out/Release/resources.pak $CHROMIUM_HOME</cmd>
<cmd>cp -a out/Release/locales $CHROMIUM_HOME</cmd>
<cmd>cp -a out/Release/resources $CHROMIUM_HOME</cmd>
<cmd>install -m0644 out/Release/chrome.1 /usr/share/man/man1</cmd>
<cmd>install -m0644 out/Release/chrome.1 /usr/share/man/man1</cmd>
<!-- We can't use system ffmpeg yet - incompability -->
<!-- chromium searchs for libav* files inside its home, so symlinks are needed -->
<!--cmd>[ -f $CHROMIUM_HOME/libavcodec.so.52 ] || ln -s /usr/lib/libavcodec.so.52 $CHROMIUM_HOME</cmd-->
<!--cmd>[ -f $CHROMIUM_HOME/libavformat.so.52 ] || ln -s /usr/lib/libavformat.so.52 $CHROMIUM_HOME</cmd-->
<!--cmd>[ -f $CHROMIUM_HOME/libavutil.so.50 ] || ln -s /usr/lib/libavutil.so.50 $CHROMIUM_HOME</cmd-->
<!-- make symlink so that chromium finds the system netscape plugins -->
<cmd>[ -f $CHROMIUM_HOME/plugins ] || ln -s /usr/lib/mozilla/plugins $CHROMIUM_HOME/plugins</cmd>
<!-- install icons on the hicolor theme path -->
<cmd>for size in 16 22 24 32 48 64 128 256; do install -m 0644 -D chrome/app/theme/chromium/product_logo_${size}.png /usr/share/icons/hicolor/${size}x${size}/apps/chromium-browser.png ; done</cmd>
<cmd>[ -f /usr/bin/chromium ] || ln -s $CHROMIUM_HOME/chromium-launcher.sh /usr/bin/chromium</cmd>
<text dest="/usr/share/applications/chromium-chromium.desktop" mode="0644">
[Desktop Entry]
Name=Chromium
Type=Application
Comment=Open-source version of Google Chrome web browser
Exec=chromium %U
TryExec=chromium
Icon=chromium-browser
Categories=Network;WebBrowser;
</text>
<cmd>[ -d /usr/share/gnome-control-center/default-apps ] || mkdir -p /usr/share/gnome-control-center/default-apps</cmd>
<text dest="/usr/share/gnome-control-center/default-apps/chromium.xml" mode="0644">
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!DOCTYPE default-apps SYSTEM "gnome-da-list.dtd"&gt;
&lt;default-apps&gt;
&lt;web-browsers&gt;
&lt;web-browser&gt;
&lt;name&gt;Chromium&lt;/name&gt;
&lt;executable&gt;chromium&lt;/executable&gt;
&lt;command&gt;chromium %s&lt;/command&gt;
&lt;icon-name&gt;chromium-browser&lt;/icon-name&gt;
&lt;run-in-terminal&gt;false&lt;/run-in-terminal&gt;
&lt;/web-browser&gt;
&lt;/web-browsers&gt;
&lt;/default-apps&gt;
</text>
</archive>
</script>
</build>
</release>
</releases>
</package>


 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez
Profile   Private Message   E-Mail
Created: 2010-07-23 03:00
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Senior Mitglied
 
 
 
Posts: 216
Registered: 2008-07-04
Hi everyone,
ritchy just added the chromium package to the repository so you don't need to build it, the x86_64 already finished building and the x86 is still building, so in about more one or 2 hours you should be able to just upkg-install chromium to get chromium on your paldo installation
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez
Profile   Private Message   E-Mail
Created: 2010-07-23 17:38
Highlight selected Text   Edit   Delete   Quote Reply
 Re: Google Chromium
Senior Mitglied
 
 
 
Posts: 216
Registered: 2008-07-04
Hi everyone, so it appears that the package is not building on x86, but works fine on x86_64

I still don't know why because I don't have the build logs.

I think it is a problem with sse2 being enabled by default. if it is, then adding -Ddisable_sse2=1 to the configuration line would fix the compilation, but I can't test it, since I have x86_64 only.
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez
Profile   Private Message   E-Mail
Created: 2010-07-24 01:15
Highlight selected Text   Edit   Delete   Quote Reply
This topic contains further posts. Next
Page: 1 2
Subscribe Topic Subscribe Topic
powered by bitron board 1.23a