View Single Post
Old 08-03-2009, 08:10 AM   #15
lunohod
OpenInkpot developer
lunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toyslunohod shares his or her toys
 
Posts: 211
Karma: 5627
Join Date: Mar 2008
Location: Stuttgart, Germany
Device: N516,V3,PRS505,iLiad,eSlick,E60,K3,K4NT,M90,PB912,KoboMini
Quote:
Originally Posted by vdevan View Post
1. How do I compile to V3update.bin since I have the rootfs-armel directory without having to revisit the web for updates.
Manually. You have to look how it is done in build-fw.

Another way is to setup a local proxy that will store all downloaded packages.
http://iplinux.org/wiki/PackageCaching

Quote:
Can the Build-FW just use the source directory as parameter, so it should not have to fetch files everytime? mk3update seems to do this without any issue for Jinke & its clones firmware.
No. We usually do not build FW too often. We build single packages and test them on the device. The FW is only being built for a new snapshot.

mk3update is different, it can only pack the existing rootfs and kernel to the V3update.bin file.

Quote:
2. If I do make a change and want to compile to a V3update.bin, what is the procedure. Should I have to load that in git? Would it not impact existing file there?
Standard way is to build a deb package or a single binary, copy them to the device and test.
If the changes are OK, you can send them to the package maintainer and he will merge them into the corresponding git repo.
lunohod is offline