Re: [SHR] toolchain (again)
Am Freitag 20 August 2010, 01:04:55 schrieb W. B. Kranendonk: Hi List, I'd like to start trying to contribute to the Openmoko-ecosystem in a more meaningful manner than lurking the mailinglists. I also like to see if I can add my own twist to my phone (running SHR-U). I imagined combining those two wishes by getting a toolchain running and see what happens to the code I put through it. Hi, there is a problem with a toolchain for SHR-U: in SHR-unstable eglibc and gcc changes really often. If one of those changes the whole toolchain needs to be recompiled, because every lib needs to be build with the current eglibc and gcc version to run properly. In this case you would have to download a new toolchain about every week, because of that there is no toolchain for SHR-U. So to build an app for SHR-u you have to set up a bitbake enviroment like discribt in [1] and then create a recipe for your app like discribet in [2]. But this is a long process, it needs about 10 hours on my PC (2,8GHz core2duo, 8Gb ram) and downloads about 15Gb of data, so a more powerfull machine then your laptop would be good. If you don't have another PC you can come to the #openmoko-devel IRC channel, perhaps we can find a solution for you. Greets Thomas [1] http://shr-project.org/trac/wiki/Building%20SHR [2] http://shr- project.org/trac/wiki/Howto%20get%20my%20application%20in%20the%20SHR%20feed ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader sales and the future of Openmoko
Hi, I have been watching the conversation about Android and its openness, and I think that Timo's answer is the closest. You should also remember that while Android is associated with Google, and certainly they had the greatest say of it, that other companies of the Open Handset Alliance also had input to Android and how it unfolded. Finally, Android is a sample implementation. The ones who last touch it before it goes on a device are the handset manufacturers. They are the ones who really determine what device drivers are used. And they, in turn, are affected by the component manufacturers and what they will allow to be released in the way of sources or even information on the devices. Finally, the carriers also have a hand in this. The carriers really do not want to see an open phone, where people can change the OS. They fear it, and perhaps for some good reasons (or what they think are good reasonsbut are really not so good reasons) such as network security. This is why most of the phones not only are locked, but also use only signed binaries. I doubt that the manufacturers care about signed binaries (although it might cut down a bit on warranty support costs) and they definitely do not care about locked phones (other than unlocked phones might piss off their favorite customers, the carriers). Looking at the original OHA, you see the unholy alliance: o component manufacturers (some infamous for how closed they are) o handset manufacturers (HTC) o codec manufacturers and licensors o carriers and finally Google (one ring to bind them all) the drum-beater. But like a lot of drum-beaters, they could only beat the drumthey were bound by contracts and agreements to do things. Even the mighty Google can not do everything they want to do. Google's (and the OHA's) methodology in engaging the community was not the best IMHO, but also can be explained by the way that the project evolved. I think that Chromium OS is going along much nicer, and I still hope that Android will eventually evolve into a real Open Source project.assuming that Oracle does not kill Android at the same time that they try to kill JAVA. Of course some people may still argue that Android is not open. I am not going to waste my time with that argument, but I just wanted to put a few more facts into the evaluation. Warmest regards, md P.S. for those of you who might be interested, I am typing this from the Amsterdam airport on my way to the FrOSCon 2010 conference in Bonn, Germany this weekend. Perhaps I will see some of you there. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader sales and the future of Openmoko
[cut] and finally Google (one ring to bind them all) the drum-beater. But like a lot of drum-beaters, they could only beat the drumthey were bound by contracts and agreements to do things. Even the mighty Google can not do everything they want to do. Great summary :) [cut] -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Email secured by Check Point ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] toolchain (again)
--- On Fri, 8/20/10, Thomas Zimmermann m...@vdm-design.de wrote: (...) 8Gb ram) and downloads about 15Gb of data, so a more powerfull machine then your laptop would be good. Hahah... The harddisk is 20GB.. I lend my desktop (with about 3GHz single core AMD a bit more up to date) to my sister... Perhaps she likes a new laptop ;-) If you don't have another PC you can come to the #openmoko-devel IRC channel, perhaps we can find a solution for you. Budget allowing, there's a new laptop coming later this year (yahoo!). Time allowing I'll join the channel, thanks! Boudewijn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] toolchain (again)
On 8/20/10, W. B. Kranendonk wankelwan...@yahoo.com wrote: --- On Fri, 8/20/10, Thomas Zimmermann m...@vdm-design.de wrote: (...) 8Gb ram) and downloads about 15Gb of data, so a more powerfull machine then your laptop would be good. Hahah... The harddisk is 20GB.. I lend my desktop (with about 3GHz single core AMD a bit more up to date) to my sister... Perhaps she likes a new laptop ;-) If you don't have another PC you can come to the #openmoko-devel IRC channel, perhaps we can find a solution for you. Budget allowing, there's a new laptop coming later this year (yahoo!). Time allowing I'll join the channel, thanks! Hi, it is not the right way to do it but you may try downloading the old OM toolchain, replace the opkg sources (then opkg-target upgrade) with the shr ones and pray :). I think for a first start in the SHR world until you have your new laptop it could work maybe. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] toolchain (again)
it is not the right way to do it but you may try downloading the old OM toolchain, replace the opkg sources (then opkg-target upgrade) with the shr ones and pray :). I think for a first start in the SHR world until you have your new laptop it could work maybe. Praying is not my strongest, let alone most used, talent, but I'll give it a try for starters ;-) Boudewijn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] toolchain (again)
On Fri, Aug 20, 2010 at 04:09:05AM -0700, W. B. Kranendonk wrote: it is not the right way to do it but you may try downloading the old OM toolchain, replace the opkg sources (then opkg-target upgrade) with the shr ones and pray :). I think for a first start in the SHR world until you have your new laptop it could work maybe. Praying is not my strongest, let alone most used, talent, but I'll give it a try for starters ;-) Boudewijn You can also try newer toolchain from Angstrom http://www.angstrom-distribution.org/toolchains/ angstrom-next is using almost the same toolchain as we're, but wasn't published for armv4t yet http://www.angstrom-distribution.org/toolchains/next/ or try to generate own sdk image with narciuss http://www.angstrom-distribution.org/narcissus sdk toolchain options are shown only after switching to advanced options, but there is no option for angstrom-next.. Regards, -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader sales and the future of Openmoko
On 20 Aug 2010 10:55:00 +0200 openm...@pulster.de (Christoph Pulster) (CP) wrote: Google can not do everything they want to do. They photograph my home without my permission, anyone can photo your house without your permission. as for google, afaik you can file a request not to be displayed. P. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] toolchain (again)
On Fri, Aug 20, 2010 at 01:37:32PM +0200, Martin Jansa wrote: On Fri, Aug 20, 2010 at 04:09:05AM -0700, W. B. Kranendonk wrote: it is not the right way to do it but you may try downloading the old OM toolchain, replace the opkg sources (then opkg-target upgrade) with the shr ones and pray :). I think for a first start in the SHR world until you have your new laptop it could work maybe. Praying is not my strongest, let alone most used, talent, but I'll give it a try for starters ;-) Boudewijn You can also try newer toolchain from Angstrom http://www.angstrom-distribution.org/toolchains/ angstrom-next is using almost the same toolchain as we're, but wasn't published for armv4t yet http://www.angstrom-distribution.org/toolchains/next/ or try to generate own sdk image with narciuss http://www.angstrom-distribution.org/narcissus sdk toolchain options are shown only after switching to advanced options, but there is no option for angstrom-next.. Regards, And fresh new SHR toolchain: http://build.shr-project.org/shr-unstable/sdk/ -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] toolchain (again)
And fresh new SHR toolchain: http://build.shr-project.org/shr-unstable/sdk/ And fresh it is! Long live SSH, allowing me to run it on a remote desktop (should have thought of that before :-) ) Downloaded the files and now extracting to /usr/local/shr/* Am I correct in understanding that I can follow the openmoko wiki with those toolchains? (shr--20100820-x86_64-linux-armv4t-linux-gnueabi-toolchain + extras) Boudewijn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] toolchain (again)
--- On Fri, 8/20/10, Martin Jansa martin.ja...@gmail.com wrote: angstrom-next is using almost the same toolchain as we're, (...) http://www.angstrom-distribution.org/narcissus sdk toolchain options are shown only after switching to advanced options, but there is no option for angstrom-next.. Ha, but there IS an option for A780 and SmartQ :-) By the way, thanks for on demand toolchain creation! Boudewijn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
