Derek Buitenhuis <[email protected]> writes: > On 14/09/2012 5:16 PM, Måns Rullgård wrote: >> ar does not touch the contents of the individual files. Does lib.exe >> add something extra to the archive that ar does not? > > The linker needs it in MSVC's .lib format in order to correctly handle > objects with the same name (e.g. mlpdsp.o). This affects debug > linking.
That is actually a broader problem. Quoth POSIX: If two or more file operands have the same last pathname component (basename), the results are unspecified. We thus ought to fix this by renaming the offending files. >>> 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? > > As it stands, we don't actually require having binutils or gcc at all > with msvc, EXCEPT for ar. I'm not at all objecting to supporting lib.exe, I just want it done properly, and I want to understand how it is different. -- Måns Rullgård [email protected] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
