Thread: iLiad FBReader
View Single Post
Old 04-09-2007, 03:52 PM   #69
narve
iLiad fan
narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.narve can teach chickens to fly.
 
Posts: 210
Karma: 3864
Join Date: Oct 2006
Device: iRex iLiad
Quote:
Originally Posted by Adam B.
Download the files again. Use this link: http://projects.mobileread.com/iliad...r/fbreader.zip It is a different binary.
Already on it (no patience today), but the copying takes some time... I think the iLiad is a bit overworked perhaps :S

Quote:
Originally Posted by Adam B.
As far as hard coding, most programs are compiled to run from /usr/ or /usr/local/. It doesn't so much matter for the executable file, but the other files that it depends on. FBReader looks for it's graphics is /usr/local/share by default. /usr/local will need to point to /mnt/free/newspapers/fbreader, not a directory within local. There is no /usr/local in the iLiad by default, so this won't cause a problem.
This seems like a sub-optimal solution. What if I have another program with the same "problem"? Why don't we instead create a "local" dir and then a "share" dir in that one, and then symlink to the directory/ies that FBReader need(s)? And I still don't see the need for different binaries, as symlinking should resolve that need?

Anyway, will try the new binaries when my iLiad wants to talk to me again. The copying is going nowhere, fast, and a see a click on the reset button looming in the horizon...
narve is offline   Reply With Quote