[FFmpeg-devel] [PATCH] Install the mingw import libraries, too

[Måns Rullgård]

Diego Biurrun <diego at biurrun.de> writes:

> On Mon, Jul 13, 2009 at 09:09:11PM -0300, Ramiro Polla wrote:
>> On Mon, Jul 13, 2009 at 8:24 PM, Diego Biurrun<diego at biurrun.de> wrote:
>> > On Mon, Jul 13, 2009 at 11:40:29PM +0300, Martin Storsj? wrote:
>> >> On Mon, 13 Jul 2009, M?ns Rullg?rd wrote:
>> >> > >> 2) Creating both SHLIBDIR and LIBDIR in install-lib$(NAME)-shared
>> >> > >
>> >> > > Not in the common code. Maybe add a mkdir to SLIB_INSTALL_EXTRA_CMD.
>> >> > > Mans, what do you think?
>> >> >
>> >> > That could work.
>> >>
>> >> Ok, the attached patch does this, but using install instead of mkdir for
>> >> stylistic reasons.
>> >>
>> >> --- a/configure
>> >> +++ b/configure
>> >> @@ -1710,7 +1710,9 @@ case $target_os in
>> >> ? ? ? ? ?SLIBNAME_WITH_MAJOR='$(SLIBPREF)$(FULLNAME)-$(LIBMAJOR)$(SLIBSUF)'
>> >> ? ? ? ? ?SLIB_EXTRA_CMD='-lib.exe /machine:$(LIBTARGET) /def:$$(@:$(SLIBSUF)=.def) /out:$(SUBDIR)$(SLIBNAME_WITH_MAJOR:$(SLIBSUF)=.lib)'
>> >> ? ? ? ? ?SLIB_INSTALL_EXTRA_CMD='-install -m 644 $(SUBDIR)$(SLIBNAME_WITH_MAJOR:$(SLIBSUF)=.lib) "$(SHLIBDIR)/$(SLIBNAME:$(SLIBSUF)=.lib)"; \
>> >> - ? ? ? ? ? ?install -m 644 $(SUBDIR)$(SLIBNAME_WITH_MAJOR:$(SLIBSUF)=.lib) "$(SHLIBDIR)/$(SLIBNAME_WITH_MAJOR:$(SLIBSUF)=.lib)"'
>> >> + ? ? ? ? ? ?install -m 644 $(SUBDIR)$(SLIBNAME_WITH_MAJOR:$(SLIBSUF)=.lib) "$(SHLIBDIR)/$(SLIBNAME_WITH_MAJOR:$(SLIBSUF)=.lib)"; \
>> >> + ? ? ? ? ? ?install -d "$(LIBDIR)"; \
>> >> + ? ? ? ? ? ?install -m 644 $(SUBDIR)lib$(SLIBNAME:$(SLIBSUF)=.dll.a) "$(LIBDIR)/lib$(SLIBNAME:$(SLIBSUF)=.dll.a)"'
>> >
>> > I think this should go in LIB_INSTALL_EXTRA_CMD instead, not SLIB_..
>> >
>> > Are both the standard .a static libs required or just the .dll.a libs?
>> 
>> I don't understand what you're asking. .dll.a files are import
>> libraries used to link the executable against DLLs. They are built and
>> should get installed even with --disable-static.
>
> OK, but then this stuff should be installed in the place where the
> shared libs go, not where the static libs are placed.

No, that's not how windows "works".  The paths are correct per my
understanding.

-- 
M?ns Rullg?rd
mans at mansr.com