[Ffmpeg-devel] more stuff for win32

[Måns Rullgård]

"Axel Holzinger" <aholzinger at gmx.de> writes:

> Hello Ramiro et all,
>
> first of all good to hear that somebody is addressing the win32 issues :-)

Windows is inherently broken.  Cygwin does a reasonably good job of
hiding much of that brokenness.  Personally, I can't be bothered
spending much time supporting a fringe platform natively when there is
already a compatibility layer available.

>> Hello,
>> 
>> I have done some changes in the makefiles for better support for win32.
>> 
>> The first removes ldconfig from the main Makefile if CONFIG_WIN32 
>> is set. Well, it doesn't remove, it just doesn't add it. I know 
>> the ldconfig line can fail and the make will still go on (because 
>> of the - sign), but this is just a suggestion.
>
> Can't comment on that, cause I'm not so much into makefiles :-)

I'd rather keep the makefile clean than keeping the make output tidy
on obscure platforms.

>> The second changes common.mak and fixes the problems with 
>> SLIBNAME_WITH_MAJOR for win32. When CONFIG_WIN32 is set, making 
>> SLIBNAME doesn't make SLIBNAME_WITH_MAJOR first to call ln later, 
>> it just builds SLIBNAME directly. This fixes the problem with the 
>> dlls with version number not being found.
>
> This is extremely helpful. The version numbers in the DLL filenames
> aren't really optimal, mainly because of one DLL pointing to the
> other. As soon as you have a new version, you have to replace all
> 3 DLLs and change your application to load the new ones. So many
> thanks for this. I will give it a try ASAP.

The point is that when the version number changes the ABI is no longer
compatible.  You have to rebuild your app in either case.  The
difference is that with version numbers you get a nice error message
instead of random crashes.

>> Additionally the patch 
>> installs the .lib files in the "$(prefix)/lib" folder so that I 
>> don't have to copy them to the Visual Studio's lib folder 
>> everytime. I just point the linker to this folder and never copy 
>> anything to Visual Studio's lib folder.

This should be possible to do without too much makefile clutter.  I
don't like the way the proposed patch does it though.

-- 
M?ns Rullg?rd
mru at inprovide.com