search

antimof / UxPlay

AirPlay Unix mirroring server
GNU General Public License v3.0
1.41k stars 190 forks source link

libcrypto-3-x64.dll not found when opening uxplay.exe on windows 10 #126

Open strawbberrys opened 1 year ago

strawbberrys commented 1 year ago

built with msys64, works fine when running it on there but when running it on windows like it says it throws that error. also if it meant windows terminal, that just does nothing when running it.

fduncanh commented 1 year ago

please repost your issue at https://github.com/FDH2/UxPlay

see https://github.com/antimof/UxPlay/issues/114

fduncanh commented 1 year ago

In Windows 10 64 bit Terminal, it works.

C:\Users\username> C:\msys64\mingw64\bin\uxplay
UxPlay 1.63: An Open-Source AirPlay mirroring and audio-streaming server.
using system MAC address xx:xx:xx:xx:xx:xx
Initialized server socket(s)
Accepted IPv4 client on socket 7200
Local: 192.168.1.8
Remote: 192.168.1.141
Client identified as User-Agent: AirPlay/675.4.1
Accepted IPv4 client on socket 7196
Local: 192.168.1.8
Remote: 192.168.1.141
raop_rtp_mirror starting mirroring
Begin streaming to GStreamer video pipeline
strawbberrys commented 1 year ago

In Windows 10 64 bit Terminal, it works.


C:\Users\username> C:\msys64\mingw64\bin\uxplay

UxPlay 1.63: An Open-Source AirPlay mirroring and audio-streaming server.

using system MAC address xx:xx:xx:xx:xx:xx

Initialized server socket(s)

Accepted IPv4 client on socket 7200

Local: 192.168.1.8

Remote: 192.168.1.141

Client identified as User-Agent: AirPlay/675.4.1

Accepted IPv4 client on socket 7196

Local: 192.168.1.8

Remote: 192.168.1.141

raop_rtp_mirror starting mirroring

Begin streaming to GStreamer video pipeline

Doesn't for me. Nothing happens whenever I run it. Possibly fixed in an update

fduncanh commented 1 year ago

built with msys64, works fine when running it on there but when running it on windows like it says it throws that error. also if it meant windows terminal, that just does nothing when running it.

what exactly is your issue? you have it working in windows in the msys64 teminal, but nothing happens in the windows terminal? so why not use the msys64 terminal?

strawbberrys commented 1 year ago

because the tutorial states it is usable in the windows terminal. opening the msys64 terminal each time can get annoying as well.