<br><br><div class="gmail_quote">On Wed, May 28, 2008 at 1:00 AM, Andy Green <<a href="mailto:andy@openmoko.com">andy@openmoko.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Somebody in the thread at some point said:<br>
| On 5/26/08, Andy Green <<a href="mailto:andy@openmoko.com" target="_blank">andy@openmoko.com</a>> wrote:<br></div><div class="Ih2E3d">
| Somebody in the thread at some point said:<br>
|<br>
| | No package 'libjana' found<br>
| | No package 'libjana-ecal' found<br>
| | No package 'libjana-gtk' found<br>
| |<br>
| | Any ideas, suggestions or can anyone provide with the required<br>
libraries ?<br>
|<br>
| Presumably the actual target libs you want are sitting there in the OM<br>
| distribution packages, and the includes and other bits and bobs are<br>
| likewise just sitting there in the -dev OM distribution packages.<br>
|<br>
|<br>
|> I was able to package a working toolchain (atleast it builds<br>
|> openmoko-dialer2) which includes the missing libs mentioned above and<br>
|> few others. As you said most of the libs were included the OM dist.<br>
|<br>
| What we need is to enable to install these into the toolchain somehow,<br>
| rather than make that a special "do it at the factory" operation to get<br>
| things into toolchain.<br>
|<br>
|<br>
|> Agreed, but till that time if anyone is interested in the toolchain I<br>
|> can put it up somewhere.<br>
<br></div>
Hey good job Pranav.<br>
<br>
After 7 months of proposing this methodology I finally get a taker --<br>
from outside OM. Maybe in another 7 months we can get a host-side opkg</blockquote><div><br>Hmm, so within OM you guys don't prefer/advise using pre-built toolchains? Any particular reason?<br><br>For me, it seems too tedious to setup the OM dev env to build single app like the dialer or some other app like squid-cache. I think the toolchain is very useful, especially for small apps, test programs or even OM apps, which just needs a small personalized modification. Anyway, thats just my thought.<br>
<br>But that brings another question (which probably needs another thread), where do we store/host the ported apps if we have some? <br>* Can we put it somewhere on <a href="http://downloads.openmoko.org">downloads.openmoko.org</a><br>
* Should we create another project on <a href="http://project.openmoko.org">project.openmoko.org</a>. <br>* Or do we put the responsibility on whoever ported it, to host the app. <br><br>-- Pranav<br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
or even unpack helper scripts as part of the toolchain so people can use<br>
it for building against their own packaged libs in a coherent way.<div class="Ih2E3d"><br>
<br>
- -Andy<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
Comment: Using GnuPG with Fedora - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a><br>
<br></div>
iEYEARECAAYFAkg9EQ4ACgkQOjLpvpq7dMrX4wCfZ4XorL+QSzSO6yiXFmRqA9oX<br>
PfMAnAw2AsWMOHJogII3VFRFtfRw99bx<br>
=KutW<div><div></div><div class="Wj3C7c"><br>
-----END PGP SIGNATURE-----<br>
<br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org" target="_blank">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br>