Skip to content

Commit a4e0a5e

Browse files
danyeawlazka
authored andcommitted
Update MINGW_INSTALLS to MINGW_ARCH
1 parent 6d33928 commit a4e0a5e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

web/wiki/Creating-Packages.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -142,13 +142,13 @@ Create a `PKGBUILD` describing all the steps necessary to build and package the
142142

143143
Run the makepkg command (`makepkg` or `makepkg-mingw`) on your recipe.
144144

145-
`makepkg-mingw` is essentially a wrapper that does a few checks, sets up the correct environments and runs `makepkg` twice, once for **mingw32** and once for **mingw64**. If you want to build just for one architecture (e.g. if you're on 32-bit Windows), you'll need to define `MINGW_INSTALLS` in the environment, with either `mingw32` or `mingw64` as the value, for example:
145+
`makepkg-mingw` is essentially a wrapper that does a few checks, sets up the correct environments and runs `makepkg` twice, once for **mingw32** and once for **mingw64**. If you want to build just for one architecture (e.g. if you're on 32-bit Windows), you'll need to define `MINGW_ARCH` in the environment, with either `mingw32` or `mingw64` as the value, for example:
146146

147-
MINGW_INSTALLS=mingw32 makepkg-mingw -sCLf
147+
MINGW_ARCH=mingw64 makepkg-mingw -sCLf
148148

149149
... or you could export it from `~/.profile` so it's set up automatically:
150150

151-
export MINGW_INSTALLS=mingw32
151+
export MINGW_ARCH=mingw64
152152

153153
Note that if you want to contribute, we'd appreciate it if you test your packages on both architectures (32 and 64 bits), which is only possible on a 64-bit Windows system. If you can't do that for some reason, we can test your pull requests on a 64-bit system.
154154

0 commit comments

Comments
 (0)