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
Externalize custom channels #9525
base: master
Are you sure you want to change the base?
Conversation
bb3d6e7
to
2318d40
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
a476767
to
fb3d364
Compare
Refer to this link for build results (access rights to CI server needed): |
fb3d364
to
65c81a7
Compare
Refer to this link for build results (access rights to CI server needed): |
65c81a7
to
d9273ae
Compare
Refer to this link for build results (access rights to CI server needed): |
d9273ae
to
06e8c40
Compare
Refer to this link for build results (access rights to CI server needed): |
@freerdp-bot test please |
Refer to this link for build results (access rights to CI server needed): |
* move rdp2tcp to custom channels (loadable at runtime) * remove code in core library (use /svc:rdp2tcp to load)
currently shared libraries are required to link as the channnels are loaded at runtime
06e8c40
to
f09b374
Compare
Refer to this link for build results (access rights to CI server needed): |
split custom channels from core library, prefer
/dvc:<channelname>
or/svc:<channelname>
syntax