| |
@@ -137,7 +137,7 @@
|
| |
-DCMAKE_INSTALL_LIBDIR:PATH=%{mingw32_libdir} \\\
|
| |
${MINGW_CMAKE_ARGS} \\\
|
| |
${MINGW32_CMAKE_ARGS} \\\
|
| |
- "$@" $__mingw32_topdir
|
| |
+ $__mingw32_topdir
|
| |
|
| |
%mingw32_cmake \
|
| |
MINGW32_CMAKE_ARGS="${MINGW32_CMAKE_ARGS} -DINCLUDE_INSTALL_DIR:PATH=%{mingw32_includedir}" \
|
| |
@@ -173,7 +173,7 @@
|
| |
--infodir %{mingw32_infodir} \\\
|
| |
${MINGW_MESON_ARGS} \\\
|
| |
${MINGW32_MESON_ARGS} \\\
|
| |
- "$@" $__mingw32_topdir
|
| |
+ $__mingw32_topdir
|
| |
|
| |
%mingw32_description This is the cross-compiled version of this library / tool.\
|
| |
You should only install this package if you want to cross-compile programs for \
|
| |
$@
is not used by the RPM macro in RPM since it is executed as a line by itself, not a script or function (at least, as I understand it, sincemingw_configure
don't use it.)There's already a
$@
in themingw-scripts.sh
file, so when expanded from the macro, the script contains two$@
, sending redundant arguments to cmake and meson.This duplication breaks things like
mingw32_meson build-directory
because the macro determines the source directory (as$__mingw32_topdir
) and replaces"$@" $__mingw32_topdir "$@"
producingbuild-directory source-directory build-directory
, which confuses meson.