building with -mms-bitfields

[Christian Ehrlicher]

Till Adam schrieb:
> On Friday 22 May 2009 16:15:45 Christian Ehrlicher wrote:
>> Till Adam schrieb:
>>> Folks,
>>>
>>> while debugging a nasty struct packing problem with gpgme, on Windows, we
>>> found out that it is normally built with -mms-bitfields, which forces
>>> packed structs, among other things. This is the setting used by msvc, and
>>> mingw has an option for it. The reason for gpgme to use it is that gtk
>>> uses it as does glib, which is one of the event loop options for gpgme.
>>> Since binaries built with -mms-bitfields are incompatible with those who
>>> have not (yes, also for plain C libraries, not just c++), there are two
>>> options. Either we provide a custom built gpgme, as part of KDE/Kontact
>>> on Windows and continue to build our binaries without that flag, or we do
>>> what the majority of other mingw based projects seem to be doing, add the
>>> flag to all builds. I'd suggest the later. Opinions?
>> Does this mean that we need to compile all dependencies with this flag?
>> This isn't really possible...
> 
> Yes, I believe so. My guess would be that many external depdencies already do 
> this, as gtk requires it, on Windows, among many other packages (according to 
> google). Stuff like libjpeg should thus definitely already have it.
> 
We don't use much binary packages from anywhere and I *neveR* saw this
compiler flag in any of the packages I built (and which were not
cmake'ified).
If you want to change this feel free to do so - I won't do it for sure.


Christian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/kde-windows/attachments/20090527/5c1a7cf9/attachment.sig