Stephan Kulow said the following, On 2007-04-12 11:00: >>>> On win32 we support two compilers to compile kde4. Because they're >>>> binary incompatible, it is not possible to mix mingw and msvc libs and >>>> executables and we have to take care that the end-user does not get >>>> into this situation. Also msvc is not supported by the open-source >>>> version of Qt4. >>>> So my question is - are there any objections against the plan to >>>> release binaries for mingw only? >>>> If not - can we somewhere write this down to avoid a discussion why not >>>> to release msvc binaries in the future? >>> I can see how it could matter for the reader of kdelibs.com - but why >>> would it >>> matter for those downloading the release? Is there something I don't see? >> The Problem for the user is that he downloads a program compiled for mingw >> but only has installed msvc libs which does not work. -> The user is >> confused. > > When you say msvc libs you're talking about kdelibs compiled with msvc, right? > If we only support mingw shipments as you suggest, I don't see that danger. I > see no advantage for shipping msvc too - beside to developers. And these libs > we need to hide well under cryptic names :)
I thought the goal is to have libs for both compilers kept even in one dir, thanks to prefixes/suffixes? Users do not care - chances are some apps will be available as msvc-only and some as mingw-only, just because developers preference. Users want latest stable version of an app... -- regards / pozdrawiam, Jaroslaw Staniek Sponsored by OpenOffice Polska (http://www.openoffice.com.pl/en) to work on Kexi & KOffice: http://www.kexi.pl/en, http://www.koffice.org KDE3 & KDE4 Libraries for MS Windows: http://kdelibs.com, http://www.kde.org _______________________________________________ release-team mailing list [EMAIL PROTECTED] https://mail.kde.org/mailman/listinfo/release-team
