[MPlayer-dev-eng] [PATCH] Mac OS X Application Bundle Support

[Chris Roccati]

On 11 Nov 2004, at 21:46, Diego Biurrun wrote:
> This should be no problem, the path you specify need not be absolute, 
> it can
> well be relative, just look at Sascha's MinGW packages.  There the
> ressources are in an mplayer/ directory relative to the package root.  
> You
> can unzip the package anywhere you want, it will work from any 
> directory.

To do so, the cygwin/mingw32 hack uses the package path as the user's 
home directory. Under MacOSX the user *HAS* an home directory, where a 
.mplayer subdir could contain user specific informations. Given the way 
mplayer gets his configuration, generally like:

(1)
  if(!get_some_config_file(get_path("/some.config.file"))) {
    if(!get_some_config_file(HARDCODED_PATH)) {
      mp_msg(...)
    }
  }

the get_path() function should do something like:

  if exists configfile in user's homedir
    return homedir + configfile
  else
    return application_dir + configfile (or whatever other "default" 
file)

if get_path() becomes so smart, there's no reason to do the (1): 
get_path() would deal with the cascade of tests and return the 
preferred path or NULL...