[Bug 673784] Rename Request: mingw32-filesystem -> cross-filesystem - Cross compiler base filesystem and environment

bugzilla at redhat.com bugzilla at redhat.com
Sun Jan 30 18:35:53 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=673784

--- Comment #5 from Erik van Pienbroek <erik-fedora at vanpienbroek.nl> 2011-01-30 13:35:51 EST ---
As mentioned on the link in the initial message the plan is to rename all
current mingw32-* package to cross-*. The idea behind this is that packagers
can maintain packages for multiple targets using a single spec file. Initially
we will support the Win32 and Win64 targets in this framework, but support for
Mac OS X can be added quite easily (it has been proven to work in a testing
repository, see the link in the initial message for more about that)

I'm okay with using a different prefix like the crossdesktop-* which Richard
suggested if you prefer that

The target name x86_64-w64-mingw32 might look a bit odd for outsiders, but it's
the default target name used by the mingw-w64 developers. I just dropped the
question about the history behind that name in the #mingw-w64 IRC channel and I
got multiple answers back. The main reason is compatibility. Think about the
autotools where a large amount of checks look for the term 'mingw32' in the
target to find out whether the target is a MS Windows one. When the 'w64' part
in the target name is used certain compiler features become available like
unicode startup (important for kernel-mode drivers and unicode features apps)
and more. More details about this can also be found at
https://sourceforge.net/apps/trac/mingw-w64/wiki/Feature%20list and
http://www.ruby-forum.com/topic/217754

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the package-review mailing list