English Portuguese (Brazil)
* Sun Apr 15 2012 Erik van Pienbroek <epienbro@fedoraproject.org> - 1.0.0-1
- Initial release
Compilation of binaries
Correct dependency generation is done automatically. Packagers should start their spec files with this line:
Cross compiled MinGW packages must follow Fedora policy, except where noted in this document. Cross compiled packages go through the same review process, GIT admin process etc. as other Fedora packages.
Debuginfo subpackage
MinGW compiled example library.
%description -n mingw32-example
MinGW compiled example library for the Win32 target.
%description -n mingw32-example-static
Static version of the MinGW Win32 compiled example library.
%description -n mingw64-example
MinGW compiled example library for the Win64 target.
%description -n mingw64-example-static
Static version of the MinGW Win64 compiled example library.
Do not use %\{mingw32_bindir}/* or %\{mingw32_libdir}/* in %files section
Each cross compiled MinGW package which builds binaries for a specific target should put the binaries for that target in a separate subpackage. So if a package `+foo+` builds binaries for the Win32 and Win64 targets, then the source RPM should provide two subpackages named `+mingw32-foo+` and `+mingw64-foo+`.
Example Specfile
Executables (EXEs)
Executables which are required for proper functionality of the libraries must be packaged in the matching mingw32/mingw64 subpackage. All other executables are discouraged, but may be packaged in optional (dependent) subpackages at a packager's discretion.
Filenames of the cross-compilers and binutils
%files -n mingw32-example-static
%files -n mingw32-foo -f mingw32-foo.lang
%files -n mingw64-foo -f mingw64-foo.lang
%files -n mingw64-example-static