[Scummvm-devel] Release 1.3.0 status -- 2010-04-24
Tarek Soliman
tarek-spam at zeusmail.bounceme.net
Wed Jun 29 23:02:40 CEST 2011
On Tue, May 24, 2011 at 02:20:49PM +0200, Frantisek Dufka wrote:
> On 24.5.2011 13:01, Max Horn wrote:
> > 3) The configure script changes have luckily shrunk to only one change: libdir is being twiddled with:
> > -libdir='${exec_prefix}/lib'
> > +libdir='${exec_prefix}/lib/scummvm'
> > and later
> > - DEFINES="$DEFINES -DPLUGIN_DIRECTORY=\\\"$libdir/scummvm\\\""
> > + DEFINES="$DEFINES -DPLUGIN_DIRECTORY=\\\"$libdir\\\""
> > To be honest, I forgot what that was about, could you remind me? It seems like a "do nothing" change, unless somebody wants to use the --libdir option. Well, in that case, just do the same thing as the WebOS port, that is:
> >
> > --- a/configure
> > +++ b/configure
> > @@ -2973,7 +2973,7 @@ case $_backend in
> > # Add ../plugins as a path so plugins can be found when running from a .PND.
> > DEFINES="$DEFINES -DPLUGIN_DIRECTORY=\\\"../plugins\\\""
> > ;;
> > - webos)
> > + maemo | webos)
> > # The WebOS app wants the plugins in the "lib" directory
> > # without a scummvm sub directory.
> > DEFINES="$DEFINES -DPLUGIN_DIRECTORY=\\\"$libdir\\\""
> >
>
> Yes, that's the reason, I don't want to have /opt/scummvm/lib/scummvm
> inside /opt/scummvm when I specify --libdir=/opt/scummvm/lib
>
> /opt/{package} is default Maemo 5 location as a workaround to
> limitation of N900 flash based storage.
>
> IMO my configure patch should be commited for all unless it breaks
> something since when I specify --libdir I really mean it! I hate when
> current scummvm configure decides to add /scummvm even if I explicitly
> said what I want libdir to be.
>
> And as you said, when no --libdir is specified there is no change.
>
Frantisek, the debian/rules file for 1.2.1 doesn't specify --libdir for the configure step.
Is this change still necessary? Am I looking in the wrong place?
--
Tarek
More information about the Scummvm-devel
mailing list