[MPlayer-cygwin] get_path cygwin

[Diego Biurrun]

Joey Parrish writes:
> On Sun, Nov 28, 2004 at 08:24:08PM +0100, Diego Biurrun wrote:
> > On Sat, Nov 27, 2004 at 07:04:29PM -0600, Joey Parrish wrote:
> > > 
> > > Absolutely not.  If you are custom compiling it to run in a cygwin
> > > environment, just specify the data path with configure.  My patch to
> > > look in the executable's directory ONLY makes sense for a packaging
> > > environment where there is no cygwin environment and the installation
> > > location is unknown at compile time.
> > 
> > Apparently this would be a desirable feature for Mac OS X as well to build
> > an app bundle (or whatever it's called), see the thread on dev-eng.
> 
> Well, OSX has to do it a different way than Windows anyway.

Not quite, just look at the thread

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

> Package maintainers have always had to keep a patch set for
> packaging because packages are always different.  I fail to see why
> so many packagers want every tiny tweak to the install environment
> committed to CVS.  It makes no sense.  I have a huge patch set to my
> packages.  Anything that seems like it belongs in CVS, I try to
> commit.  But a lot of things don't belong, and this, IMHO, is one of
> them.

I disagree.  Apparently we have at least three platforms that could
benefit from loading configuration etc files from a path relative to
the executable, namely MinGW, Mac OS X, Cygwin and possibly others.
This is not a tweak for one package on one architecture so it's
definitely worth putting in CVS IMO.

Diego