jam7 / chrome-cross Goto Github PK

View Code? Open in Web Editor NEW

7.0 7.0 3.0 103 KB

Easy to build chromebook toolchains environment with docker

License: GNU General Public License v3.0

Makefile 12.67% Shell 87.33%

chrome-cross's People

Contributors

Stargazers

Watchers

Forkers

snailium lovedheart

chrome-cross's Issues

lib32 and lib64

I don't own chromebook x86_64, so I'm not sure what they needs. Currently, I made only lilb64 libraries for gcc under /usr/local/lib64 and other 64 bits libraries in /usr/local/lib. Is it OK? Should I made all libraries for both 64 and 32 bits?

Reducing the file sizes

Has using an utility like strip on the final binaries been up for consideration?
http://www.linuxfromscratch.org/lfs/view/6.7-rc1/chapter06/aboutdebug.html
http://www.linuxfromscratch.org/lfs/view/6.7-rc1/chapter06/strippingagain.html

Ruby/git/libssh2

Have you considered building and packaging ruby, git and libssh2 with the toolchains?
It would be nice to have those packages prebuilt and hosted on the same location as gcc for the chromebrew project.

Change from sha1 to sha256?

We're doing this over at https://github.com/skycocker/chromebrew.

gcc 7.1.0

It is theoretically possible to use the latest gcc on chromebook. Glibc and binutils won't since part of them are the part of chromebook, but gcc doesn't.

This may solves compiler internal error problem at chromebrew/chromebrew#697.

Recommend Projects