Hendrik Leppkes <[email protected]> writes:
> On Fri, Sep 14, 2012 at 11:04 PM, Måns Rullgård <[email protected]> wrote:
>
>> Hendrik Leppkes <[email protected]> writes:
>>
>> > This allows building with Microsofts version of ar
>> > by specifying --ar='c99wrap lib.exe' during configure.
>> > ---
>> > configure | 11 +++++++++++
>> > library.mak | 2 +-
>> > 2 files changed, 12 insertions(+), 1 deletion(-)
>> >
[...]
>> > +probe_cc ar "$ar"
>> > +ARFLAGS=${_arflags-$ARFLAGS}
>> > +AR_O=${_ar_o-$AR_O}
>>
>> This is a bit weird. The probe_cc function is meant to be used with
>> commands that invoke the compiler driver (gcc etc) in some manner. The
>> 'ar' command does not fit this category.
>
> I put it there because the probing code does manage quite nicely to
> identify the tool, and set the vars accordingly.
> Alternative approach is welcome.
It works in this particular case, yes. Because it's a different tool,
it might not work with other implementations.
>> What is the advantage of using lib.exe instead of ar anyway?
>
> It allows to properly retain the objects debug information, ar doesn't
> manage that for some reason.
ar does not touch the contents of the individual files. Does lib.exe
add something extra to the archive that ar does not?
> I also think its a good idea to be able to build without grabbing any part
> of gcc or binutils.
We require piles of gnu tools anyway, so what's one more?
--
Måns Rullgård
[email protected]
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
