![]() |
Google Chrome compile on Slack64
Hello everyone,
I am using slack-current x64 and I tried to compile chrome x64 (slackbuild). I started 35 minutes ago and chrome compile process is still running. I could not understand why does it take very long time? P.S. : I installed all dependencies of chrome (yasm, libevent, gnome-keyring,nss...) |
Chromium is a huge package to compile. Perhaps you were looking for the binary repackaging of Google-Chrome?
http://slackbuilds.org/repository/13...google-chrome/ Google-Chrome only requires GConf (+Orbit2), while Chromium requires yasm, libevent, gnome-keyring (+other libs). |
Quote:
|
Quote:
The link that disturbed1 provided to SlackBuilds.org does not compile google-chrome. The SlackBuild script downloads the pre-compiled binaries from Google and then repackages the binaries into a slack package. |
Quote:
I bolded my post as well in case it's skipped over while being read. AFAIK you can NOT compile Google Chrome, only the open source Chromium. |
Quote:
One of my major concerns (vanity strikes again) was that I spent years in front of green screens, then 14" amberchromes coz some psychologists decided that the old green phosphor screens made you want to commit suicide, and then finally living in a world of 256 shades of gray... So I wanted a "color" logo (chromium is b&w). I still don't really have a good reason for deciding between the two of them. hm... that reminds me. I need to check on why sbopkg didn't tell me to upgrade it. Aw, it prolly did and I didn't want to coz I would prolly have to put the user agent line in again, LOL. Anyway, what I find most interesting, and didn't know, was the extra libs required to intstall chromium. Why is that? |
Quote:
|
| All times are GMT -5. The time now is 05:19 AM. |