[Caprice32-devel] Re: Linux binary package

[Stephane M. <mar...@ic...>]

> 
> > - under unix, programs usually install to a different place than the
> > one
> > they subsequently run. Usually /usr/ or /usr/local. That can cause
> > some
> > trouble to find the configuration file for example. Here are some
> > ideas :
> > * add the ability to load files (especially the config file) from
> > different places at compile time
> > * add the ability to auto detect the path it runs from, and use this
> > path
> > as a base to find where (we hope) the config file lies
> 
> :)  I don't know if you've looked at that particular part of the source
> yet,
> but we're actually doing the latter already. And AFAIK, it works - if
> not,
> we need to fix that ASAP!
>

Ok, I'm not sure we're talking about the same thing.
The path you use is the current path that the shell uses, which doesn't 
take into account the path typed. For example if I do :

[/home/steph/]$ ./caprice32/cap32
The path is "/home/steph" and the config files aren't found.
I'll have to dig, but there's a function that does this IIRC (i.e. find
the path to the current binary).

Stephane