Thread: iLiad iLiad 3rd Party programs standardization
View Single Post
Old 04-18-2007, 07:10 PM   #2
smoogle
That dude with the thing
smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.smoogle once ate a cherry pie in a record 7 seconds.
 
Posts: 20
Karma: 1904
Join Date: Apr 2007
Device: iLiad
Some further comments;

It is possible (and I intend to), make the new code for relocation to be done as a .patch file; allowing us to apply it to whichever version we wish. It is also to our advantage, that code like that in fbreader/etc is not often (if ever) changed across revisions.

I agree entirely with the LD_LIBRARY_PATH stuff; but another neat thing I thought of-

We could make a program to run on startup, and verify er_registry.txt; a common problem I understand is if the file is not valid, the iLiad won't start the contentlister? So i'm going to work on a program that checks if the file is valid; if the file isn't valid for some reason, then it can use a safe backup.

Also, fyi you can find out where symbolic links point to, but I don't think it's too imporant? We can just have the script update the location each time it's run (not like creating a symbolic link is a time-consuming process anyway).
smoogle is offline   Reply With Quote