xpra icon
Bug tracker and wiki

Opened 8 months ago

Closed 6 months ago

Last modified 7 weeks ago

#1483 closed task (fixed)

workaround broken MSYS2 dependencies

Reported by: Antoine Martin Owned by: Antoine Martin
Priority: major Milestone: 2.1
Component: packaging Version: trunk
Keywords: win32 Cc:


MSYS2 is a rolling distro, which means that occasionally some packages will be out of sync and need a rebuild. Occasionally, those rebuilds can be tricky... or just fail.
r15493 makes it possible to ship the older dependencies by simply dropping them in the win32\bundle-extra directory, this just gets bundled automatically in the installation directory.
This hack was needed because opencv has not yet been rebuilt since the libwebp soname got bumped.

But for this hack to work, we need to still have the old library around..
So maybe we need to take regular snapshots of the msys installation directory? PITA.

Change History (3)

comment:1 Changed 8 months ago by Antoine Martin

Status: newassigned

I did have the old libwebp-6.dll on my 64-bit build VM, but not on the 32-bit one... and since the rebuild of opencv still fails, the 32-bit builds will just moan about webcam support until opencv is fixed upstream.

See also ticket:678#comment:55 which is a similar issue with libgfortran-3.dll

Last edited 7 weeks ago by Antoine Martin (previous) (diff)

comment:2 Changed 6 months ago by Antoine Martin

Resolution: fixed
Status: assignedclosed

Works well enough, and 64-bit builds are now the default.

comment:3 Changed 7 weeks ago by Antoine Martin

Another issue worth recording here: the opencv package updates have new hard dependencies but those are not installed automatically, breaking the package (so no webcam):

export XPKG="mingw-w64-${MSYSTEM_CARCH}-"
pacman -S ${XPKG}glog ${XPKG}ceres-solver ${XPKG}gflags ${XPKG}protobuf

And as of today, opencv is still broken on 64-bit systems. Trying to run "import cv2" fails with Invalid access to memory location.

Last edited 7 weeks ago by Antoine Martin (previous) (diff)
Note: See TracTickets for help on using tickets.