As a library, lws is always just a component in a bigger application.
When users have a problem involving lws, what is happening in the bigger application is usually critical to understand what is going on (and where the solution lies).
Many users are able to share their sources, but others decide not to, for presumed "commercial advantage" or whatever. (In any event, it can be painful looking through large chunks of someone else's sources for problems when that is not the library author's responsibility.)
This makes answering questions like "what is wrong with my code I am not going to show you?" or even "what is wrong with my code?" very difficult.
Even if it's clear there is a problem somewhere, it cannot be understood or reproduced by anyone else if it needs user code that isn't provided.
The biggest question is, "is this an lws problem actually"?
The test server and client are extremely useful for sanity checks and debugging guidance.
test apps work on your platform, then either
test apps break on your platform, but work on, eg, x86_64, either
test apps break everywhere
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。