[MPlayer-dev-eng] configuration patch to allow setting of ar from the commandline

Diego Biurrun diego at biurrun.de
Thu Aug 23 19:35:42 CEST 2007


On Thu, Aug 23, 2007 at 10:22:09AM -0400, Marc Hoffman wrote:
> On 8/16/07, Marc Hoffman <mmhoffm at gmail.com> wrote:
> > On 8/16/07, Diego Biurrun <diego at biurrun.de> wrote:
> > > On Thu, Aug 16, 2007 at 09:04:56AM -0400, Marc Hoffman wrote:
> > > >
> > > > I was thinking it might be real nice to configure
> > > > those automatically somehow.  I'm not sure how one might go about
> > > > this.  Here is a stab at it just so you get the idea.  Most configure
> > > > environments support this type of target option and default tools
> > > > setup.
> > > >
> > > > .e.g. given on the commandline --target=xxx-yyy-zzz then:
> > > > _cc=${_target}-gcc
> > > > ...
> > > >
> > > > You really do need to run the commandline twice or, make it have this
> > > > type of semantics when its the first ac_option.
> > >
> > > I don't see why it needs to be run twice ..
> > >
> > So you can override it.  if we do it at the end of the the loop i.e.
> > just check if target is set and then setup cc, as, ... then you can't
> > set them by hand. (which someone might want to do)  If I put it in the
> > loop i.e. where target is currently caught then its commandline
> > position dependent. (which might be ok)
> 
> I never got a definitive answer on this Diego.

I have to admit that I still fail to see what you are missing and why
you think you have to scan the command line twice to achieve this.  Yes,
options that are repeated on the command line should override all
previous occurrences.

Diego



More information about the MPlayer-dev-eng mailing list