Hendrik Leppkes <[email protected]> wrote:
>On Sat, Sep 15, 2012 at 1:36 PM, Måns Rullgård <[email protected]> wrote: > >> Hendrik Leppkes <[email protected]> writes: >> >> > On Fri, Sep 14, 2012 at 11:46 PM, Måns Rullgård <[email protected]> >wrote: >> >> >> >> Now, can we all work together to fix it? >> >> >> >> >> > So coming back to lib.exe, whats your suggestion for a correct >approach? >> > A special probe function that trys to detect which "ar" is being >used, >> > similar to probe_cc, but separate? >> >> What does a proper lib.exe command line look like? >> >> >lib.exe -nologo -out:libavcodec/libavcodec.a <long list of .o files> > >In make terms, this would be: >lib.exe -nologo -out $@ $^ > >Note that c99wrap translates from "-out foo" to "-out:foo" so msys path >expansion can do its thing. FWIW, I'm not sure if msys path expansion is needed for ar/lib.exe - as long as all the provided paths are relative, the official form (-out:foo, and skipping using c99wrap) should work. For link.exe, absolute paths aren't used in the actual build, only during configure (for stuff like /tmp/foo), IIRC. OTOH, that makes it inconsistent with the link parameters, so I don't have too much of an opinion either way. // Martin _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
