[MPlayer-dev-eng] deterministic builds

[Attila Kinali]

On Sat, 20 Dec 2003 20:32:19 +0100
Enrico Weigelt <weigelt at metux.de> wrote:


> Okay, its syntactic sugar. But it would be better to have an kind
> of "standard" for as many projects as possible.

Not really, people tent to think that their solution is the best.
Beside, a standard always restricts people and sometimes these
restrictions are too much a burden.

 
> <snip>
> > > * many feature options are only available as --enable-xxx or --disable-xxx
> > >   (the default setting seems not to be supported as explicit parameter)
> > 
> > It's the default, why do you need an explicit parameter to specify it in
> > the first place?  
> Can I rely that this standard always remains the same ?

Not really, the default for 99% of the options is autodetect and
use if available (only a few options which are highly experimental
are disabled by default). 


> <snip>
> > > * there seems to be no way for finding out what build configuration 
> > >   configure is in fact using.
> > 
> > After it's done, read config.h and config.mak that it generated.  This
> > is the most complete description of what it decided.  Also, see
> > configure.log for details, although this would be more difficult for a
> > machine to parse and understand.
> Is this output machine readable (parsable with acceptable work) ?
> Can I rely on the consistence of the format over newer versions ?

config.h and config.mak are both machine readable, infact they have
to be read by machines, by the c compiler resp. make.
And yes, those formats wont change. But defines or variables might
be added or disapear as new options are added or obsolete ones removed.
Ie you need to keep track of the changes of the ./configure script.


				Attila Kinali
-- 
egp ist vergleichbar mit einem ikea bausatz fuer flugzeugtraeger
			-- reeler in +kaosu