Google Chrome Web Browser on TinyCore?

[baz]

I find Google Chrome to be much faster and lighter than other browsers and would love to have it on TinyCore. What can I do to make that happen?

[julianb]

I was thinking about trying to compile Chrome, but I don't have time right now. I think someone has to compile it for TC for it to work (I don't think you can just install from a .deb)

To compile, you'll want to get the extension "tc-compile".

The "google chrome source" web site can provide the source code for download and it'll tell you what libraries/dependencies need to be present at compile-time.

All of the how-to's on making a tinycore extension seem to require more indepth Linux knowlege than I have,* but I've been trying to make sense of them. You can learn more by reading the forums and the wiki.

*specifically, after having compiled a kernel extension I didn't know where the files created by "make" were, and you can't "tar" a file without knowing where it is or what it's name is.

[Arslan S.]

nss-nspr requirement does not meet in tiny core it needs to be updated first

http://code.google.com/p/chromium/wiki/LinuxBuildInstructionsPrerequisites#Software_Requirements

[Jason W]

I will update nss-nspr soon.  I followed linux from scratch build which packaged them together, but the newer LFS builds them seperate.  I will for now keep them together as to not break existing dep files and tce directory installations, and will seperate them for TC 3.0.

[Arslan S.]

I will update nss-nspr soon.  I followed linux from scratch build which packaged them together, but the newer LFS builds them seperate.  I will for now keep them together as to not break existing dep files and tce directory installations, and will seperate them for TC 3.0.

i have successfully compiled chrome from source after updating nss-nspr myself
posting from chrome at the moment

[Jason W]

If you already have an updated nss-nspr, please feel free to submit it as there it no need to duplicate work. 

[Arslan S.]

http://farm3.static.flickr.com/2493/4185688318_79591bd9b5_o.png

[Arslan S.]

If you already have an updated nss-nspr, please feel free to submit it as there it no need to duplicate work.  

when it comes to packaging i am not too good

i will submit it with chrome in a few days

[baz]

WHAT!!!!!!!!! How amazing is this community!!

[Jason W]

Arslan, I think your packaging will be fine.  It will be nice to have a chrome built from source into /usr/local as opposed to the Debian/Fedora packages they supply.

[Arslan S.]

it just runs where it is located provided that some other files alongside with it
it doesnt have an auto install option
i was thinking of puting those files under /usr/local/share/chromium
and creating a wrapper script in /usr/local/bin
for flash player support creating a symlink  $CHROME_ROOT/plugins/libflashplayer.so

but i have for now problems with licencing and how can i build it for i486
i set compiler flags in environment but dunno if building system respected those flags  

this is the link i followed with compiling
http://code.google.com/p/chromium/wiki/LinuxBuildInstructions

[Jason W]

The other Mozilla browsers are installed to /usr/local/browsername.  So /usr/local/chromium would fall in line with that, with a wrapper in /usr/local/bin.

I built Shiretoko optimized for i686, a 586 or lower machine is not going to even be able to run any of these browsers.  So I think that i686 is acceptable for apps that must have a more modern machine to run.

Licensing does seem a little unclear, and I am not sure if one can distribute a non official build as chrome or if another name must be used.  I will look further.

[bmarkus]

I built Shiretoko optimized for i686, a 586 or lower machine is not going to even be able to run any of these browsers. 

Just curious, did you try it?

[Jason W]

Though I built the original Shiretoko as i686, the subsequent builds have been -march=i486 -mtune=i686 as I have used the standard TC build flags for it. 

I will test on my 400mhz Athlon that is a 586 as I am curious, the machine I was using in the past to test i586 compatibility.   It would run Shiretoko that was built for i486, though anyone using a machine of that spec to surf the modern web with a modern browser would be quickly frustrated by it.

[Arslan S.]

i have found the licence is BSD and third party libs has own licences
http://code.google.com/intl/tr-TR/chromium/terms.html