On Tue, Dec 20, 2016 at 05:32:23PM +0100, Luca Barbato wrote: > On 20/12/2016 17:12, Diego Biurrun wrote: > > On Tue, Dec 20, 2016 at 05:00:24PM +0100, Luca Barbato wrote: > >> On 20/12/2016 15:34, Diego Biurrun wrote: > >>> This moves work from the configure to the Make stage where it can > >>> be parallelized and ensures that shared libraries are built with > >>> the right version number in the filename. > >>> --- > >>> Makefile | 2 +- > >>> build/common.mak | 2 +- > >>> build/library.mak | 5 +++++ > >>> build/libversion.sh | 15 +++++++++++++++ > >>> configure | 13 ------------- > >>> 5 files changed, 22 insertions(+), 15 deletions(-) > >>> create mode 100755 build/libversion.sh > >> > >> Possibly ok. Does it produce the same version on all the special targets? > > > > Special targets == ? > > BSD and Windows.
Literally the same Make variables are stored in a different place now: libfoo/libfoo.version instead of config.mak, so I don't expect any difference. I will of course let this run through Oracle at some point. Diego _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
