Skip to content
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

Link to SC_20 / SC_20_DEBUG in README.txt #3

Open
lwcorp opened this issue Aug 13, 2022 · 3 comments
Open

Link to SC_20 / SC_20_DEBUG in README.txt #3

lwcorp opened this issue Aug 13, 2022 · 3 comments

Comments

@lwcorp
Copy link

lwcorp commented Aug 13, 2022

The README.txt just states:

README.txt

Aug 2022

SC is now part of the ultraVNC git.
Using SC_20 or SC_20_DEBUG.

Can you add a link to both of these right in the readme?

Maybe It can be found https://github.com/ultravnc/UltraVNC/tree/SC_20_dev1/winvnc/SC_20? But where's SC_20_DEBUG?
If so, where's the source code? It only has plugins:
image

@RudiDeVos
Copy link
Member

RudiDeVos commented Jan 14, 2023

SC is now part of winvnc.
There is no different code tree, it's the same tree as winvnc.exe ( full) you just need to select SC_20 or SC_20_DEBUG in Visual Studio.
image

@lwcorp
Copy link
Author

lwcorp commented Jan 15, 2023

But can it also be seen online at https://github.com/ultravnc/UltraVNC?

@RudiDeVos
Copy link
Member

RudiDeVos commented Jan 15, 2023

No, SC does not have a seperated source.

Before, SC and UltraVNC were seperated branches.
This was to hard to maintain, so SC is now a part of UltraVNC, there is only one source used to build SC2 and UltraVNC.
It's just a compiler predefine that determ if you build SC2 or UltraVNC.

#ifdef SC_20
..
#endif
...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants