Diego Biurrun <[email protected]> writes: > On Tue, Sep 20, 2011 at 05:23:46PM +0100, Måns Rullgård wrote: >> Diego Biurrun <[email protected]> writes: >> >> > Sometimes it can be useful to build not just the default target, but some >> > different target or a list of targets in addition to the default one. >> > If the make_targets variable is set, that list of targets is built, >> > otherwise just the default target is built as usual. >> > >> > --- a/tests/fate.sh >> > +++ b/tests/fate.sh >> > @@ -61,7 +61,7 @@ configure()( >> > >> > compile()( >> > cd ${build} || return >> > - ${make} ${makeopts} && ${make} install >> > + ${make} ${makeopts} ${make_targets} && ${make} install >> > ) >> >> This is the wrong way to accomplish what you want. > > Please be constructive and say what the correct way is instead of just > hinting at issues and letting me guess. The above is tested to work on > one of my FATE instances and looks minimally intrusive to me. > > Do you want to see the compile and install step separated? If not, > what then?
Any extras should be run like any other test, resulting in an report entry. We don't want the entire build to "fail" and the run to abort just because some silly test program has an error. -- Måns Rullgård [email protected] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
