-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass server arguments over socket #1358
Comments
I got redirected here by this Google search: "scrcpy Command too long (255 chars)" My problem is that I set this
and got this:
I get this error even if I enable long path support in Windows 10 via
I was able to get around this problem with
So it looks like something in the scrcpy pipeline is limiting the path length. |
It's only limited on Windows releases by mingw. If you know a solution to extand this limit on mingw, please help. |
Though it will be a misery to deal with, did you try using Unicode Win32 functions i.e. |
I don't know the actual solution unfortunately. I mostly wanted to post the workaround as reference. However, I did a bit of digging based on how Git for Windows (it uses mingw) handles long paths (the
A blog that discusses this: Hopefully this can help! |
Thank you for the links. Note that here the problem is that the command (including the arguments) is too long, not the path of the executable. |
Yes, I also mean the command line, the second argument in |
Oh, but I'm stupid, the error scrcpy/app/src/sys/win/process.c Line 17 in a1f2094
scrcpy/app/src/sys/win/process.c Line 30 in a1f2094
🤦 |
And increase the command buffer size. Refs #1358 <#1358 (comment)> PR #2405 <#2405> Signed-off-by: Romain Vimont <rom@rom1v.com>
And increase the command buffer size. Refs #1358 <#1358 (comment)> PR #2405 <#2405> Signed-off-by: Romain Vimont <rom@rom1v.com>
I tried to improve readability/robustness of configuration passed from the client ot the server: 870ced0 (branch
name_params
)But on Windows, it failed:
I think many of these key=value pairs should be passed over the socket (not
tunnel_forward
because the socket creation depends on it).Or maybe you have a better idea?
The text was updated successfully, but these errors were encountered: