-
Notifications
You must be signed in to change notification settings - Fork 900
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
Discuss generating dynamic library #1123
Comments
I'm afraid I don't understand what issue you are trying to solve. We have no intention of being a general VNC library, so statically linking the common code makes things a lot easier for our own use. Exactly what scenario are you trying to get working? |
I want to use vnc in my project. My project only cares about interface display and keyboard and mouse operations. The specific RFB protocol is completed by this project. Therefore, this project needs to be provided in the form of a library (dynamic library and static library). |
I'm afraid that is outside the goals of this project. Maintaining a stable library is a lot of work. Doing so for C++ is much much worse. So it's unfortunately not something we can take on at this time. I suggest having a look at libvncclient. That project is designed for use as a library. |
libvncclient is C . But I need C++. maintaining a stable library is eary. |
Generate dynamic library development library to facilitate other projects. I have generated a static development library, see: #1114
The current common is divided into four sub-libraries: os, network, rdr, and rfd.
Advantage:
The classification of the library is clear.
Disadvantages:
Solution:
The text was updated successfully, but these errors were encountered: