fedora-docs-l10n/packaging-guidelines/master/pages/MinGW — English @ Fedora Weblate: [root] | +- etc | | | +- rpm

Zen

Source string Source string

English

[root]
  |
  +- etc
  |   |
  |   +- rpm
  |       |
  |       +- macros.mingw
  |       +- macros.mingw32
  |       +- macros.mingw64
  |
  +- usr
      |
      +- bin   - Links to MinGW cross compiler toolchain
      |   |
      |   +- i686-w64-mingw32-cpp
      |   +- i686-w64-mingw32-gcc
      |   +- i686-w64-mingw32-g++
      |   +- x86_64-w64-mingw32-cpp
      |   +- x86_64-w64-mingw32-gcc
      |   +- x86_64-w64-mingw32-g++
      |   +- x86_64-w64-mingw32ucrt-cpp
      |   +- x86_64-w64-mingw32ucrt-gcc
      |   +- x86_64-w64-mingw32ucrt-g++
      |   +- ... etc..
      |
      +- lib
      |   |
      |   +- rpm
      |       |
      |       +- mingw-find-debuginfo.sh - extract debug information from Win32 and Win64 binaries
      |       +- mingw-find-lang.sh - generates per-target file lists containing translations
      |       +- mingw-find-provides.sh - extra DLL names
      |       +- mingw-find-requires.sh - discover required DLL names
      |
      +- i686-w64-mingw32  - root of mingw toolchain and binaries for the Win32 target with MSVCRT runtime - see next diagram
      +- x86_64-w64-mingw32  - root of mingw toolchain and binaries for the Win64 target with MSVCRT runtime - see next diagram+`
      +- x86_64-w64-mingw32urt  - root of mingw toolchain and binaries for the Win64 target with UCRT runtime - see next diagram+`

Needs editing

The string is read only.

Skip

	English	Actions
	The goal of the MinGW framework is to provide an easy way for package maintainers to build their packages for multiple targets using one .spec file. To aid developers in this several RPM macros have been developed which are part of the mingw-filesystem package. These RPM macros will be explained later on in these guidelines.
	By default MinGW support will be built for both the Win32 and Win64 targets with the MSVCRT runtime. Building of the Win64 target with the UCRT64 runtime is not yet enabled by default.
	When a package can only be built for a subset of these targets this can be indicated by setting one or more of these:
	\|`+%global mingw_build_win32 0+` \|Don't build for the Win32 target with the MSVCRT runtime \|`+%global mingw_build_win64 0+` \|Don't build for the Win64 target with the MSVCRT runtime \|`+%global mingw_build_ucrt64 0+` \|Don't build for the Win64 target with the UCRT runtime
	One source RPM, separate binary RPMs per-target
	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 `+mingw-foo+` or `+foo+` builds binaries for the Win32 and Win64 targets with the MSVCRT runtime, then the source RPM should provide two subpackages named `+mingw32-foo+` and `+mingw64-foo+`. If a package builds for the UCRT runtime, it will also have a `+ucrt64-foo+` subpackage.
	This means that a spec file must contains %package and %files sections for all the targets.
	When using the separate packaging approach, packages containing translations must use `+%mingw_find_lang+` instead of `+%find_lang+`.
	When using the integrated packaging approach, packages containing translations must use `+%find_lang` followed by `+%mingw_find_lang+`.
	This causes all translation filelists to be split in per-target filelists. For example: when a spec file contains something like this:
	%install <snip> %mingw_find_lang foo
	then one file per mingw target will get created named `+mingw32-foo.lang+`, `+mingw64-foo.lang+`, and `+ucrt64-foo.lang+`. These file lists can be included in the %files section for the targets:
	%files -n mingw32-foo -f mingw32-foo.lang <snip> %files -n mingw64-foo -f mingw64-foo.lang <snip> %files -n ucrt64-foo -f ucrt64-foo.lang
	Filesystem layout
	Integration into the main root filesystem layout is as follows:
	[root] \| +- etc \| \| \| +- rpm \| \| \| +- macros.mingw \| +- macros.mingw32 \| +- macros.mingw64 \| +- usr \| +- bin - Links to MinGW cross compiler toolchain \| \| \| +- i686-w64-mingw32-cpp \| +- i686-w64-mingw32-gcc \| +- i686-w64-mingw32-g++ \| +- x86_64-w64-mingw32-cpp \| +- x86_64-w64-mingw32-gcc \| +- x86_64-w64-mingw32-g++ \| +- x86_64-w64-mingw32ucrt-cpp \| +- x86_64-w64-mingw32ucrt-gcc \| +- x86_64-w64-mingw32ucrt-g++ \| +- ... etc.. \| +- lib \| \| \| +- rpm \| \| \| +- mingw-find-debuginfo.sh - extract debug information from Win32 and Win64 binaries \| +- mingw-find-lang.sh - generates per-target file lists containing translations \| +- mingw-find-provides.sh - extra DLL names \| +- mingw-find-requires.sh - discover required DLL names \| +- i686-w64-mingw32 - root of mingw toolchain and binaries for the Win32 target with MSVCRT runtime - see next diagram +- x86_64-w64-mingw32 - root of mingw toolchain and binaries for the Win64 target with MSVCRT runtime - see next diagram+` +- x86_64-w64-mingw32urt - root of mingw toolchain and binaries for the Win64 target with UCRT runtime - see next diagram+`
	The bulk of the packaged content is located under the respective MinGW root, one of `+/usr/i686-w64-mingw32+`, `+/usr/x86_64-w64-mingw32+` and `+/usr/x86_64-w64-mingw32ucrt+`:
	[mingw-root] \| +- bin - Binutils toolchain binaries for the target \| \| \| +- ar \| +- as \| +- dlltool \| +- ld \| +- ... etc ... \| +- lib - Binutils toolchain support libraries / files for the target \| +- sys-root - root for cross compiled MinGW binaries \| +- mingw \| +- bin - cross-compiled MinGW binaries & runtime DLL parts +- etc - configuration files +- include - include files for cross compiled MinGW libs +- lib - cross-compiled static MinGW libraries & linktime DLL parts \| \| \| +- pkgconfig - pkg-config definitions for libraries \| +- share \| +- man
	Filenames of the cross-compilers and binutils
	The MinGW cross-compilers and binutils are Fedora binaries and are therefore placed in `+%{_bindir}+` (i.e., `+/usr/bin+`) according to the FHS and Fedora guidelines.
	The MinGW cross-compilers and binutils which generate i686 binaries for Windows with the MSVCRT runtime are named:
	%{_bindir}/i686-w64-mingw32-gcc %{_bindir}/i686-w64-mingw32-g++ %{_bindir}/i686-w64-mingw32-ld %{_bindir}/i686-w64-mingw32-as %{_bindir}/i686-w64-mingw32-strip etc.
	The same binaries are present in `+%{_prefix}/i686-w64-mingw32/bin+` without any prefix in the name, i.e.,
	%{_prefix}/i686-w64-mingw32/bin/gcc %{_prefix}/i686-w64-mingw32/bin/g++ %{_prefix}/i686-w64-mingw32/bin/ld %{_prefix}/i686-w64-mingw32/bin/as %{_prefix}/i686-w64-mingw32/bin/strip etc.
	The same also applies for the x86_64 target with both MSVCRT and UCRT runtimes. The target with MSVCRT uses 'x86_64-w64-mingw32' as prefix instead of 'i686-w64-mingw32', while UCRT uses 'x86_64-w64-mingw32ucrt'.
	Naming of the root filesystem
	The root filesystem contains Windows executables and DLLs and any other Windows-only files. It is necessary both because we need to store Windows libraries in order to link further libraries which depend on them, and also because MinGW requires a root filesystem location.
	The location for Win32 target with MSVCRT runtime is provided by the macro:
	%{mingw32_sysroot} %{_prefix}/i686-w64-mingw32/sys-root
	The Win64 target with MSVCRT runtime is provided by the macro:
	%{mingw64_sysroot} %{_prefix}/x86_64-w64-mingw32/sys-root

Loading…

None

String updated in the repository

English

English 1360 characters edited Current translation Read only

a year ago

Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English	English
No related strings found in the glossary.

12543224 String information

Source string description

type: delimited block .

Flags

no-wrap, read-only

Source string location

./pages/MinGW.adoc:279

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

pot/master/pages/MinGW.pot, string 59

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.