I have just realized that opkg-cl isn't in toolchain. :( added and committed, will show up in the next toolchain build.
On Thu, May 29, 2008 at 12:34:40PM +0800, John Lee wrote: > > libjana isn't packaged in toolchain by default. the default > compopents are: > > libmokogsmd2, mokoui2, mokopanelui2, mokojournal2 and dependencies. > > we cannot package everything or it's going to be a huge toolchain. > however, there are 2 interesting aliases in environment-setup: > > alias opkg='LD_LIBRARY_PATH=/usr/local/openmoko/arm/lib > /usr/local/openmoko/arm/bin/opkg-cl -f > /usr/local/openmoko/arm/etc/opkg-sdk.conf -o /usr/local/openmoko/arm' > > alias opkg-target='LD_LIBRARY_PATH=/usr/local/openmoko/arm/lib > /usr/local/openmoko/arm/bin/opkg-cl -f > /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf -o > /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi' > > which means by opkg-target we can add the packages we need into the > toolchain directory. > > at the moment the content of > > /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf > > is incorrectly pointed to local directories in build host. if we > replace it by the corresponding URIs such as > > http://buildhost.openmoko.org/daily-feed/ > http://buildhost.openmoko.org/daily-feed/all > http://buildhost.openmoko.org/daily-feed/armv4t > http://buildhost.openmoko.org/daily-feed/neo1973 > http://buildhost.openmoko.org/daily-feed/om-gta01 > > then _theoretically_ we can just do > > opkg-target update > opkg-target install libjana-dev > > I haven't tried this approach before because OE suits me just fine. > however, for those who just want to make apps I think it's an right way > to start. > > > Regards, > John >
