(Solved) Chromium browser - recommended install method?

[globetrotterdk]

I have tried on at least six occasions to install Chromium browser on my Salix64 KDE 13.37 install. I end up banging my head against the wall every time with build errors. I believe that I have all dependencies installed, so that begs the questions:

1) What is the recommended method for installing Chromium browser?
2) How do I purge the /tmp folder, after a build doesn't succeed? I assume it is the /tmp folder that all of this goes into?

Cheers

Edit: I should of course have added that I am trying to install Chromium using Sourcery.
----
SOLUTION (31/5-2013):

I have since tried on a nuber of occasions to build Chromium. My experience now tells me that to get a successful build of Chromium, all of the following should be installed (on a 64-bit system):

Code: Select all

# slapt-get -i libevent GConf ORBit2 google-chrome-pam-solibs seamonkey-solibs mozilla-nss yasm

[fredg]

1) I know at least two ways:
http://www.salixos.org/forum/viewtopic.php?f=20&t=3130
http://www.salixos.org/forum/viewtopic.php?f=24&t=2795

2) if you're using sourcery/slapt-src, the slackbuild do it itself:
http://slackbuilds.org/slackbuilds/13.3 ... SlackBuild

++

[EricC]

While not Chromium, I use the Google Chrome slackbuild from the Slackware 13.37 extra folder:

ftp://slackware.mirrors.tds.net/pub/sla ... le-chrome/

[globetrotterdk]

Thanks to both of you for your quick replies.
@ fredg I tried option #2, but I got the following errors:

Code: Select all

# sh chromium.SlackBuild
----snip----
Package nss was not found in the pkg-config search path.
Perhaps you should add the directory containing `nss.pc'
to the PKG_CONFIG_PATH environment variable
No package 'nss' found
----snip----
Exception: Call to 'pkg-config --cflags nss' returned exit status 1.
while loading dependencies of base/base.gyp while loading dependencies
of build/all.gyp while trying to load build/all.gyp

I couldn't figure out what the nss package was, that was being referred to.

@ EricC Wow! The Google Chrome solution went extremely smoothly, especially considering all of the problems that I have had trying to get the Chromium version up and running. Now I am a happy camper

[JRD]

Hwo this post have been marked "solved" ?
You installed Chrome, not Chromium…

[globetrotterdk]

Close enough for me.

[EricC]

Thanks to both of you for your quick replies.
@ EricC Wow! The Google Chrome solution went extremely smoothly, especially considering all of the problems that I have had trying to get the Chromium version up and running. Now I am a happy camper

I am glad I was able to provide an acceptable alternative as I have been down the road you were on