Public build host (proposal)
Hi, since it seems to be extremely difficult to build software for the OpenMoko on my home machine, perhaps it would be usefull if someone (within OpenMoko?) would set up a globally reachable build host with an openembedded and toolchain environment on it. That way, people with less experience setting up a build environment, or people not having the possibility to have one, could also build software. Let's hear a vote or proposal! Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
> Let's hear a vote or proposal! the idea crossed my mind too the other day. would be a nice thing to have but of course it requires rather much attention (far from everything in the sources buids actually and updating w/ mokomakefile seems absolutely not to pull in the newest code). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 2:18 PM, arne anka <[EMAIL PROTECTED]> wrote: > the idea crossed my mind too the other day. > would be a nice thing to have but of course it requires rather much > attention (far from everything in the sources buids actually and updating > w/ mokomakefile seems absolutely not to pull in the newest code). Well, I'd be the one building my own code. The build host 'only' needs to be up to date wrt. the compilers and openembedded stuff. No need to build 'all the code all day'. Christ -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
> Well, I'd be the one building my own code. The build host 'only' needs > to be up to date wrt. the compilers and openembedded stuff. No need to > build 'all the code all day'. not sure i understand you correctly: i thought rather of smth like a webinterface, offering a list of available packages and building a particular one on request. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 2:31 PM, arne anka <[EMAIL PROTECTED]> wrote: > not sure i understand you correctly: i thought rather of smth like a > webinterface, offering a list of available packages and building a > particular one on request. No, I want to develop my own packages, so I need a place to upload my code and get an ipkg build for me. Christ -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Wed, Jul 23, 2008 at 2:31 PM, arne anka <[EMAIL PROTECTED]> wrote: |> not sure i understand you correctly: i thought rather of smth like a |> webinterface, offering a list of available packages and building a |> particular one on request. | | No, I want to develop my own packages, so I need a place to upload my | code and get an ipkg build for me. This won't scale, folks should obviously be able to make their own packages on their own host without undue problems. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiHK2UACgkQOjLpvpq7dMrARgCfWvzh7etzWPXvqxWSMGMzZfjU uqAAnj/hWY4xy+XsuevMljx3I9r4NcQz =00bs -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 3:00 PM, Andy Green <[EMAIL PROTECTED]> wrote: > This won't scale, folks should obviously be able to make their own > packages on their own host without undue problems. I'm having 'due problems' then :-( Christ -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Wed, Jul 23, 2008 at 3:00 PM, Andy Green <[EMAIL PROTECTED]> wrote: |> This won't scale, folks should obviously be able to make their own |> packages on their own host without undue problems. | | I'm having 'due problems' then :-( Toolchain tarball is a nice way actually, but I found if you need to link against libraries not in toolchain tree magically already, things become radically less smooth. There is a install-target-lib-and-dev-package-on-build-host solution that was "incomplete" and coming but I didn't hear that it was finished yet. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiHMP0ACgkQOjLpvpq7dMpyBACdGYtJZDdsKESXYKOJFpRQrK+h 5MYAnja5Fim/7sLLOjVhnqsKPcRRtvOt =PHv7 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 3:24 PM, Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | On Wed, Jul 23, 2008 at 3:00 PM, Andy Green <[EMAIL PROTECTED]> wrote: > |> This won't scale, folks should obviously be able to make their own > |> packages on their own host without undue problems. > | > | I'm having 'due problems' then :-( > > Toolchain tarball is a nice way actually, but I found if you need to The toolchain requires one to have an i386(ish) machine. So does openmokoui2.0-dev. Mokomakefile also fails on a non-i386(ish) somewhere. Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 9:50 AM, Christ van Willegen <[EMAIL PROTECTED]> wrote: > On Wed, Jul 23, 2008 at 3:24 PM, Andy Green <[EMAIL PROTECTED]> wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Somebody in the thread at some point said: >> | On Wed, Jul 23, 2008 at 3:00 PM, Andy Green <[EMAIL PROTECTED]> wrote: >> |> This won't scale, folks should obviously be able to make their own >> |> packages on their own host without undue problems. >> | >> | I'm having 'due problems' then :-( >> >> Toolchain tarball is a nice way actually, but I found if you need to > > The toolchain requires one to have an i386(ish) machine. So does > openmokoui2.0-dev. > > Mokomakefile also fails on a non-i386(ish) somewhere. On that topic, has anyone tried compiling everything (OE) on *BSD? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Jul 23, 2008, at 5:01 AM, Christ van Willegen wrote: > Hi, > > since it seems to be extremely difficult to build software for the > OpenMoko on my home machine, perhaps it would be usefull if someone > (within OpenMoko?) would set up a globally reachable build host with > an openembedded and toolchain environment on it. I have images available as an Amazon EC2 AMI. If you are familiar with Amazon EC2 (it is really easy to set yourself up if you are not) let me know and I shall send you the details. It isnt free (it costs about $.10 per hour for the "standard" machine) but you only pay for when you are using it. - VV > > That way, people with less experience setting up a build environment, > or people not having the possibility to have one, could also build > software. > > Let's hear a vote or proposal! > > Christ van Willegen > -- > 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
greetings, collabnet, my employer, might be willing to provide cubit, a virtualized build and environment. if you're interested, I can ask. -john mark walker opencollabnet community manager On 7/23/08, Vijay Vaidyanathan <[EMAIL PROTECTED]> wrote: > > On Jul 23, 2008, at 5:01 AM, Christ van Willegen wrote: >> Hi, >> >> since it seems to be extremely difficult to build software for the >> OpenMoko on my home machine, perhaps it would be usefull if someone >> (within OpenMoko?) would set up a globally reachable build host with >> an openembedded and toolchain environment on it. > > I have images available as an Amazon EC2 AMI. If you are familiar > with Amazon EC2 (it is really easy to set yourself up if you are not) > let me know and I shall send you the details. > > It isnt free (it costs about $.10 per hour for the "standard" > machine) but you only pay for when you are using it. > > - VV > > >> >> That way, people with less experience setting up a build environment, >> or people not having the possibility to have one, could also build >> software. >> >> Let's hear a vote or proposal! >> >> Christ van Willegen >> -- >> 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > -- John Mark Walker Community Manager, CollabNet http://www.collab.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On 7/23/08, Vijay Vaidyanathan <[EMAIL PROTECTED]> wrote: > I have images available as an Amazon EC2 AMI. If you are familiar > with Amazon EC2 (it is really easy to set yourself up if you are not) > let me know and I shall send you the details. > > It isnt free (it costs about $.10 per hour for the "standard" > machine) but you only pay for when you are using it. Oh ... and if it wasn't obvious, I am not the one charging the $.1 per hour, it goes to Amazon, and they keep it :-) I'd just be the one creating and making the image available to the public. details are at http://www.amazon.com/ec2/ and I'm just a satisfied customer etc etc. - VV ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 11:59 AM, John Mark Walker <[EMAIL PROTECTED]> wrote: > greetings, > > collabnet, my employer, might be willing to provide cubit, a > virtualized build and environment. if you're interested, I can ask. > > -john mark walker > opencollabnet community manager I should note that I would request this to be gratis for Openmoko. -JM ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
by "gratis" he means "without cost" y On Wed, Jul 23, 2008 at 11:04 PM, John Mark Walker <[EMAIL PROTECTED]> wrote: > On Wed, Jul 23, 2008 at 11:59 AM, John Mark Walker > <[EMAIL PROTECTED]> wrote: >> greetings, >> >> collabnet, my employer, might be willing to provide cubit, a >> virtualized build and environment. if you're interested, I can ask. >> >> -john mark walker >> opencollabnet community manager > > > I should note that I would request this to be gratis for Openmoko. > > -JM > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 2:25 PM, Yorick Moko <[EMAIL PROTECTED]> wrote: > by "gratis" he means "without cost" > Oops... :) Yes, I mean "free as in beer." -- John Mark Walker Community Manager, CollabNet http://www.collab.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
Hi, > since it seems to be extremely difficult to build software for the > OpenMoko on my home machine, perhaps it would be usefull if someone > (within OpenMoko?) would set up a globally reachable build host with > an openembedded and toolchain environment on it. could you describe what kind of problems you experience ? The only way to improve the situation is by naming the issues at hand. :-) Marek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
John Mark Walker wrote: > On Wed, Jul 23, 2008 at 2:25 PM, Yorick Moko <[EMAIL PROTECTED]> wrote: > >> by "gratis" he means "without cost" >> >> > > Oops... :) Yes, I mean "free as in beer." > > Not to be a nitpick, but I think the official quote is "free as in free beer" which makes much more sense :). In general I have a way too hard time to find free beer. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Thu, Jul 24, 2008 at 2:16 AM, Marek Lindner <[EMAIL PROTECTED]> wrote: > > Hi, > >> since it seems to be extremely difficult to build software for the >> OpenMoko on my home machine, perhaps it would be usefull if someone >> (within OpenMoko?) would set up a globally reachable build host with >> an openembedded and toolchain environment on it. > > could you describe what kind of problems you experience ? The only way to > improve the situation is by naming the issues at hand. :-) I tried to tell you a few times, but I'll rephrase. I have an iMac G5, rev C (with iSight built-in). That is a PowerPC64 architecture. - There is no native Mokomakefile support for this machine - I tried running VirtualPC to emulate an i386 processor so that I could install Ubuntu. This works, but is _terribly_ slow. Also, getting Ubuntu 8 on it is something I didn't try. But, building Mokomakefile took days to get to step 1500. - I eventually found out how to install Debian etch on my PC (natively), but running Mokomakefile's 'make build-devel-image' gave me an error 'don't know what to do with powerpc64 architecture'. - The toolchain explicitly states that it needs i386. I could build from source, but openmokoui-2.0-dev is also only available for i386. Well, that's about it :-) A simple Ubuntu- or Debian-machine 'out there' on the Internet with up-to-date bild env and the poosibility to scp files over would be ideal now :-) I hope this sums up the problems well enough. Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Thu, 24 Jul 2008, Christ van Willegen wrote: > Well, that's about it :-) A simple Ubuntu- or Debian-machine 'out > there' on the Internet with up-to-date bild env and the poosibility to > scp files over would be ideal now :-) You can borrow an account on my machine for now if you like. Email me off-list. (Keeping the list in the loop for some reason.) -- Asheesh. -- "This is a job for BOB VIOLENCE and SCUM, the INCREDIBLY STUPID MUTANT DOG." -- Bob Violence ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
2008/7/24 Christ van Willegen <[EMAIL PROTECTED]>: > On Thu, Jul 24, 2008 at 2:16 AM, Marek Lindner <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >>> since it seems to be extremely difficult to build software for the >>> OpenMoko on my home machine, perhaps it would be usefull if someone >>> (within OpenMoko?) would set up a globally reachable build host with >>> an openembedded and toolchain environment on it. >> >> could you describe what kind of problems you experience ? The only way to >> improve the situation is by naming the issues at hand. :-) > > I tried to tell you a few times, but I'll rephrase. > > I have an iMac G5, rev C (with iSight built-in). That is a PowerPC64 > architecture. > > - There is no native Mokomakefile support for this machine > - I tried running VirtualPC to emulate an i386 processor so that I > could install Ubuntu. This works, but is _terribly_ slow. Also, > getting Ubuntu 8 on it is something I didn't try. But, building > Mokomakefile took days to get to step 1500. Instead of using the mokomakefile you could try this package I've made for Ubuntu(see http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html). The package contain the toolchain and some common libs, which makes it quite easy to get started. Furthermore the opkg-sdk is installed, which means it is pretty easy to add missing packages to the toolchain. > - I eventually found out how to install Debian etch on my PC > (natively), but running Mokomakefile's 'make build-devel-image' gave > me an error 'don't know what to do with powerpc64 architecture'. > - The toolchain explicitly states that it needs i386. I could build > from source, but openmokoui-2.0-dev is also only available for i386. > > Well, that's about it :-) A simple Ubuntu- or Debian-machine 'out > there' on the Internet with up-to-date bild env and the poosibility to > scp files over would be ideal now :-) > > I hope this sums up the problems well enough. > > Christ van Willegen > -- > 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Thu, Jul 24, 2008 at 9:19 AM, Andreas Dalsgaard <[EMAIL PROTECTED]> wrote: > Instead of using the mokomakefile you could try this package I've made > for Ubuntu(see > http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html). > The package contain the toolchain and some common libs, which makes it > quite easy to get started. Furthermore the opkg-sdk is installed, > which means it is pretty easy to add missing packages to the > toolchain. Do you suggest I re-try running Ubuntu (8) in Virtual PC or in Q(emu)? I'll try that tonight and/or tomorrow. After that, I'll be on a 2-week holiday... with my brand-spanking-new FreeRunner that I expect to get today or tomorrow! Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
> Do you suggest I re-try running Ubuntu (8) in Virtual PC or in Q(emu)? > I'll try that tonight and/or tomorrow. After that, I'll be on a 2-week > holiday... with my brand-spanking-new FreeRunner that I expect to get > today or tomorrow! Another option is to compile-on-board. Yes, thats right, add all the - dev packages for the libraries you're interested in, put gcc on your Freerunner, and do all your compiling with the Freerunner. For a lot of bootstrapping apps, this method works just fine .. ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Thu, Jul 24, 2008 at 10:29 AM, Jay Vaughan <[EMAIL PROTECTED]> wrote: > Another option is to compile-on-board. Yes, thats right, add all the - > dev packages for the libraries you're interested in, put gcc on your > Freerunner, and do all your compiling with the Freerunner. For a lot > of bootstrapping apps, this method works just fine .. I don't have any objections to having a c compiler 'on board' with me all the time... IIRC I can 'dpkg install gcc' on the FreeRunner, and also 'dpkg install openmokoui-2.0-dev'? Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
> I don't have any objections to having a c compiler 'on board' with me > all the time... Me either! In fact I find it a very easy way to get started with OpenMoko development without having all the drudgery of setting up a cross-toolchain and all the other cruft associated with it. > IIRC I can 'dpkg install gcc' on the FreeRunner, and also 'dpkg > install openmokoui-2.0-dev'? s/dpkg/opkg/, sure. Here's what I did to set up my Freerunner to compile the bling project onboard: opkg install binutils binutils-dev libc6-dev libcairo-dev linux-libc- headers-dev gcc cpp cpp-symlinks g++ g++-symlinks gcc-symlinks libstdc+ +-dev libmokoui2-dev librsvg-2-gtk-dev librsvg-2-dev make make-dev bling: http://w1xer.de/bling.html ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On 24 Jul 2008, at 06:22, Kalle Happonen wrote: > John Mark Walker wrote: >> On Wed, Jul 23, 2008 at 2:25 PM, Yorick Moko >> <[EMAIL PROTECTED]> wrote: >> >>> by "gratis" he means "without cost" >> >> Oops... :) Yes, I mean "free as in beer." > > Not to be a nitpick, but I think the official quote is "free as in > free > beer" which makes much more sense :). I have never seen the phrase used this way, only "free as in beer" (vs "free as in speech"). I think historically beer was given out on polling day, when candidates wished to influence the electorate. They would host a big party and drunk electors would go to the polling booths thinking "that guy would make a great politician because he gave me free beer". Thus the beer is not "really free". > In general I have a way too hard time to find free beer. Exactly! If someone gives you free beer then they probably want something in return! Likewise "there's no such thing as a free lunch", even if the salesman is buying. Stroller. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
Stroller wrote: > On 24 Jul 2008, at 06:22, Kalle Happonen wrote: > >> John Mark Walker wrote: >> >>> On Wed, Jul 23, 2008 at 2:25 PM, Yorick Moko >>> <[EMAIL PROTECTED]> wrote: >>> >>> by "gratis" he means "without cost" >>> Oops... :) Yes, I mean "free as in beer." >>> >> Not to be a nitpick, but I think the official quote is "free as in >> free >> beer" which makes much more sense :). >> > > I have never seen the phrase used this way, only "free as in > beer" (vs "free as in speech"). > Yes, I have always also heard it like that. But then I saw a question to Stallman, "that doesn't make sense, there's no real free beer"? And he answered that no, but people are misquoting. It was originally "free as in free speech, not as in free beer" or something pretty close... If there are some real gpl stallman enthusiast there, feel free to flame me for mistelling/quoting/having proprietary nvidia drivers on the laptop.. Kalle ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 02:25:30PM +0200, Christ van Willegen wrote: > On Wed, Jul 23, 2008 at 2:18 PM, arne anka <[EMAIL PROTECTED]> wrote: > > the idea crossed my mind too the other day. > > would be a nice thing to have but of course it requires rather much > > attention (far from everything in the sources buids actually and updating > > w/ mokomakefile seems absolutely not to pull in the newest code). > > Well, I'd be the one building my own code. The build host 'only' needs > to be up to date wrt. the compilers and openembedded stuff. No need to > build 'all the code all day'. > > Christ > -- > 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community Hi Christ, If you only wants to build your own project, I recommend you to use meta-toolchain. OpenEmbedded builds everything even if you only trying to build Hellworld. If you still wants to use OE, turn off AUTOREV may be a good try. Best Regards, -Ju1ian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
> If you only wants to build your own project, I recommend you to use > meta-toolchain. > .. or use the compiler-on-board approach. Took me 46 seconds to compile a 2000-line GTK app with cairo, rsvg, etc. Not terribly exciting, speed-wise, but definitely very easy to use if you don't want to set up a full cross-compiling build environment, and whats even greater is that you can do all the development work as a new project on your Linux machine, then just put the source files on the Freerunner for compiling/testing in that environment. My project for testing all this right now is bling, an update of the FOSDEM 2007 demo app by macslow, with changes to make it run nicely on Freerunner. This project even uses autotools, so its very nice and easy to go from the main Linux workstation in my life to the Freerunner for final compiling after development .. > OpenEmbedded builds everything even if you only trying to build > Hellworld. Once you get it set up once, you can then just use "bitbake -b myrecipefile.bb" to build only your local project, though .. ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Thu, Jul 24, 2008 at 07:27:37AM +0200, Christ van Willegen wrote: > On Thu, Jul 24, 2008 at 2:16 AM, Marek Lindner <[EMAIL PROTECTED]> wrote: > I tried to tell you a few times, but I'll rephrase. > > I have an iMac G5, rev C (with iSight built-in). That is a PowerPC64 > architecture. > > - There is no native Mokomakefile support for this machine > - I tried running VirtualPC to emulate an i386 processor so that I > could install Ubuntu. This works, but is _terribly_ slow. Also, > getting Ubuntu 8 on it is something I didn't try. But, building > Mokomakefile took days to get to step 1500. > - I eventually found out how to install Debian etch on my PC > (natively), but running Mokomakefile's 'make build-devel-image' gave > me an error 'don't know what to do with powerpc64 architecture'. > - The toolchain explicitly states that it needs i386. I could build > from source, but openmokoui-2.0-dev is also only available for i386. > > Well, that's about it :-) A simple Ubuntu- or Debian-machine 'out > there' on the Internet with up-to-date bild env and the poosibility to > scp files over would be ideal now :-) > > I hope this sums up the problems well enough. > > Christ van Willegen Hi Christ, Sorry I didn't see this mail before I reply the previous mail. Right now we only build images and toolchain on x86. Maybe you can discuss this issue on the mailing list of OpenEmbedded. Paste your error message and ask for someone who has experience on this :-) Best Regards, -Ju1ian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On Wed, Jul 23, 2008 at 02:24:13PM +0100, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > Toolchain tarball is a nice way actually, but I found if you need to > link against libraries not in toolchain tree magically already, things > become radically less smooth. There is a > install-target-lib-and-dev-package-on-build-host solution that was > "incomplete" and coming but I didn't hear that it was finished yet. > > - -Andy Hi Andy, I am working on this. Right now I had build some packages successful like splinter. And the dependency librarys were install from buildhost. I am trying to integrate those stuffs into meta toolchain, hopes I can release new toolchain before everybody kill me :P Best Regards, -Ju1ian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Wed, Jul 23, 2008 at 02:24:13PM +0100, Andy Green wrote: |> -BEGIN PGP SIGNED MESSAGE- |> Hash: SHA1 |> Toolchain tarball is a nice way actually, but I found if you need to |> link against libraries not in toolchain tree magically already, things |> become radically less smooth. There is a |> install-target-lib-and-dev-package-on-build-host solution that was |> "incomplete" and coming but I didn't hear that it was finished yet. |> |> - -Andy | | Hi Andy, | |I am working on this. |Right now I had build some packages successful like splinter. And the |dependency librarys were install from buildhost. That's going to be great. It'll definitely make a big difference to any dev wanting to build for Freerunner. |I am trying to integrate those stuffs into meta toolchain, hopes I |can release new toolchain before everybody kill me :P Don't worry, soon as you release it everyone will want to marry you instead :-) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiId7EACgkQOjLpvpq7dMpjXACbBKfT68QhWCjQIfnKE2hSyaxk DTkAn0zjNEjF9oTHQyW3fydHwV7CmD1V =9Pcr -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
Marek Lindner wrote: > Hi, > >> since it seems to be extremely difficult to build software for the >> OpenMoko on my home machine, perhaps it would be usefull if someone >> (within OpenMoko?) would set up a globally reachable build host with >> an openembedded and toolchain environment on it. > > could you describe what kind of problems you experience ? The only way to > improve the situation is by naming the issues at hand. :-) > > Marek > I have yet to get a single application to build on my Ubuntu machine. Everything I've tried ends up missing some library or other and the instructions for adding libraries not in the toolchain are totally unclear to me. (Also, it seems like some extremely basic libraries are not in the toolchain, so that makes no sense to me either.) Finally, there was discussion on this list, in another thread, I think, that much of the toolchain's .la files still refer to gta01 or neo1973 directories and that this causes a lot of problems. I'm not sure if that's what is causing my issues or something else, but I'll echo what another list member said: One would think that a working toolchain would be a priority. Brian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
Try an older version of the Toolchain: http://downloads.openmoko.org/toolchains/ I've had good luck with the 20071211 build. But couldn't get the same app to compile with the latest build (20080521). Hopefully we'll get an updated and working Toolchain shortly (someone is working on it from what I've read). -Steven On Thu, Jul 24, 2008 at 11:16 AM, Brian C <[EMAIL PROTECTED]> wrote: > Marek Lindner wrote: >> Hi, >> >>> since it seems to be extremely difficult to build software for the >>> OpenMoko on my home machine, perhaps it would be usefull if someone >>> (within OpenMoko?) would set up a globally reachable build host with >>> an openembedded and toolchain environment on it. >> >> could you describe what kind of problems you experience ? The only way to >> improve the situation is by naming the issues at hand. :-) >> >> Marek >> > > I have yet to get a single application to build on my Ubuntu machine. > Everything I've tried ends up missing some library or other and the > instructions for adding libraries not in the toolchain are totally > unclear to me. (Also, it seems like some extremely basic libraries are > not in the toolchain, so that makes no sense to me either.) Finally, > there was discussion on this list, in another thread, I think, that much > of the toolchain's .la files still refer to gta01 or neo1973 directories > and that this causes a lot of problems. I'm not sure if that's what is > causing my issues or something else, but I'll echo what another list > member said: One would think that a working toolchain would be a priority. > > Brian > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
If you are running Ubuntu you could try out: http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html If you experience any problems please drop me a mail. 2008/7/24 Brian C <[EMAIL PROTECTED]>: > Marek Lindner wrote: >> Hi, >> >>> since it seems to be extremely difficult to build software for the >>> OpenMoko on my home machine, perhaps it would be usefull if someone >>> (within OpenMoko?) would set up a globally reachable build host with >>> an openembedded and toolchain environment on it. >> >> could you describe what kind of problems you experience ? The only way to >> improve the situation is by naming the issues at hand. :-) >> >> Marek >> > > I have yet to get a single application to build on my Ubuntu machine. > Everything I've tried ends up missing some library or other and the > instructions for adding libraries not in the toolchain are totally > unclear to me. (Also, it seems like some extremely basic libraries are > not in the toolchain, so that makes no sense to me either.) Finally, > there was discussion on this list, in another thread, I think, that much > of the toolchain's .la files still refer to gta01 or neo1973 directories > and that this causes a lot of problems. I'm not sure if that's what is > causing my issues or something else, but I'll echo what another list > member said: One would think that a working toolchain would be a priority. > > Brian > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Public build host (proposal)
On 24/07/08 13:17:49, Julian Chu wrote: >dependency librarys were install from buildhost. > >I am trying to integrate those stuffs into meta toolchain, hopes I >can release new toolchain before everybody kill me :P > > Best Regards, > > -Ju1ian > I hope the *.la files for the libs have correct paths in them this time, because I had to half kill my machine to get gtk related stuff to compile. Michael. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: Public build host (proposal)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jay Vaughan wrote: > > I don't > have any objections to having a c compiler 'on board' with me >> all the time... > > > Me either! In fact I find it a very easy way to get started with > OpenMoko development without having all the drudgery of setting up a > cross-toolchain and all the other cruft associated with it. > >> IIRC I can 'dpkg install gcc' on the FreeRunner, and also 'dpkg >> install openmokoui-2.0-dev'? > > > > s/dpkg/opkg/, sure. > > Here's what I did to set up my Freerunner to compile the bling project > onboard: > > opkg install binutils binutils-dev libc6-dev libcairo-dev > linux-libc-headers-dev gcc cpp cpp-symlinks g++ g++-symlinks > gcc-symlinks libstdc++-dev libmokoui2-dev librsvg-2-gtk-dev > librsvg-2-dev make make-dev > > bling: > > http://w1xer.de/bling.html > > ; > -- > Jay Vaughan > > > > > > > This is a vast relief. With the demise of my laptop I'll be depending on my freerunner for compiling stuff. Also: the openmoko toolchain: why is it only distributed as binary!? I have the source code for GCC, Binutils, etc, but their configure scripts don't seem to like --target=ARM-Linux-guneabi - tips anyone? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIiQtXjK3MZIZPmKIRAvw/AKCyorWYopbxEy3TQ87gaSUjLViu9gCfQ4Z9 dU253nBKIy+e/WzWSl0MZZU= =zmMF -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
