Hi guys,
In building the mingw-w64-pyqt4 package I found an odd behavior I don't
know how to debug - it s probably a quirk of the qmake build process; I
used the same msys2 configuration to do other packages without a problem.
The build proceeded until a packaging error:
cd pyrcc/ && make -f Makefile install
make[1]: Entering directory
'/f/github/MINGW-packages/mingw-w64-pyqt4/src/python2-i686-w64-mingw32/pyrcc'
make -f Makefile.Release install
make[2]: Entering directory
'/f/github/MINGW-packages/mingw-w64-pyqt4/src/python2-i686-w64-mingw32/pyrcc'
cp -f "release/pyrcc4.exe"
"/f/github/MINGW-packages/mingw-w64-pyqt4/pkg/mingw-w64-i686-python2-pyqt4/mingw/msys32/mingw32/bin/pyrcc4.exe"
make[2]: Leaving directory
'/f/github/MINGW-packages/mingw-w64-pyqt4/src/python2-i686-w64-mingw32/pyrcc'
make[1]: Leaving directory
'/f/github/MINGW-packages/mingw-w64-pyqt4/src/python2-i686-w64-mingw32/pyrcc'
mv: cannot stat
‘/f/github/MINGW-packages/mingw-w64-pyqt4/pkg/mingw-w64-i686-python2-pyqt4/mingw32/bin/pyuic4.bat’:
No such file or directory
==> ERROR: A failure occurred in package_mingw-w64-i686-python2-pyqt4().
Aborting...
translation: the "mv" command didn't execute correctly.
This command is from the PKGBUILD, routine package_python2-pyqt4 :
mv "${pkgdir}${MINGW_PREFIX}"/bin/{,python2-}pyuic4.bat
i.e., letting top=/f/github/MINGW-packages/mingw-w64-pyqt4,
with pkgdir=${top}/pkg/mingw-w64-i686-python2-pyqt4/
then for MINGW_PREFIX=mingw32, ${pkgdir}${MINGW_PREFIX} will be the above
target. but the directory structure that was created for the build, where
I found the files, was
${top}
-
- pkg
- mingw-w64-i686-python2-pyqt4
- - mingw
- - msys32
- - - mingw32
So it seems to have taken my root path D:/mingw/msys32, stripped away the
D: and inserted those two two extra directories before the business end of
the build. The build went ok - all the files were there - but it was in
the wrong place.
For reference:
greg@Homerw7 MSYS ~
$ cat /etc/fstab
# For a description of the file format, see the Users Guide
# http://cygwin.com/cygwin-ug-net/using.html#mount-table
# DO NOT REMOVE NEXT LINE. It remove cygdrive prefix from path
none / cygdrive binary,posix=0,noacl,user 0 0
D:/mingw /mingw
C:/msys64 /msysC
E:/cygwin64 /cygwin
greg@Homerw7 MSYS ~
$ ls /mingw
bld32 COPYING.LIB info opt64-psxseh versions
bld32dw2 DMingw msys32 pkg
x86_64-4.9.1-posix-seh
COPYING gdl-0.9.5 opt32-psxdw2 plplot-5.11.0-dyn zzz
greg@Homerw7 MSYS ~
$ cygpath -w /
D:\mingw\msys32\
I then repeated the build from an msys2 installation in the standard
location (rooted at C:/msys64) and had no such issue with building the
package:
${top}
-
- pkg
- mingw-w64-i686-python2-pyqt4
- mingw32
The contents of mingw32/ were identical except for the resulting
python2-pyuic4.bat (The first one I renamed by hand)
for C:/msys64 root path:
@C:/msys64/mingw32/bin/python2.exe
/mingw32/lib/python2.7/site-packages/PyQt4/uic/pyuic.py %1 %2 %3 %4 %5 %6
%7 %8 %9
for D:/mingw/msys32 root path:
@D:/mingw/msys32/mingw32/bin/python2.exe
/mingw/msys32/mingw32/lib/python2.7/site-packages/PyQt4/uic/pyuic.py %1 %2
%3 %4 %5 %6 %7 %8 %9
Regards,
Greg
------------------------------------------------------------------------------
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
