dev builds
themes manual
device status forums
mailing lists
IRC bugs
dev guide

Rockbox mail archive

Subject: Re: [RaaA] Weekly status report

Re: [RaaA] Weekly status report

From: Frank Gevaerts <>
Date: Mon, 14 Jun 2010 16:27:16 +0200

On Mon, Jun 14, 2010 at 04:14:59PM +0200, Thomas Martitz wrote:
> I'm sorry that I left out the last week's report, the uni kept me busy
> this week (forunately at least the devcon attenders are aware of my
> progress). But it paid of, my Rockbox presentation went really really
> well :P
> Back to the topic: My project is in a good shape I think. I can actually
> build an SDL application right now (not defining SIMULATOR or any
> target). You can look at the code at
> However, it's not quite finished yet. To make it distributable I have to
> work out how to the file system and how to install it.
> a) We collected some ideas two weeks ago but we didn't manage to find a
> consensus I think. I still think exposing the full / is unnecessary but
> OTOH I wouldn't want to limit users. But it could also be annoying to
> always start off at / when browsing for music. I guess we need a way to
> link/mount (configurable) directories into the start point of the file
> browser for convinience but then it could get tricky with the database
> (I fear the redundancy would make it list files multiple times).

If needed, it shouldn't be too hard to check if one configured directory
is entirely inside another one (just plain string comparisons). The
trivial way to check this can of course fail if people get creative with
partial relative paths or symlinks, but then They Shouldn't Do That.

> b) Where to install it? /usr/local/bin (or C:\Program Files\Rockbox)
> comes into my mind, but then there's the problem of not having write
> access in the installation routine. Installing somewhere into $HOME
> seems weird. Another idea would be installing the binaries to
> /usr/local/bin, the plugins/codecs to /usr/local/share, and see what
> changes are needed to de-attach them from the .rockbox directory.

That would be ideal I think (except the plugins and codecs should go to
$PREFIX/lib, not $PREFIX/share, they are architecture dependent)

Don't hardcode the prefix, leave it as a define to be given as e.g.
-DPREFIX="/usr/local". That's easy to do, and makes things a lot more
flexible for people.


> Best regards.

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
Received on 2010-06-14

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy