-
-
Notifications
You must be signed in to change notification settings - Fork 208
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
fix: discord-rpc in cmake #925
base: main
Are you sure you want to change the base?
Conversation
b393e83
to
31695c5
Compare
"cmaker" and "vs release" in RPC, huh? Did you add it yourself for test? :)
Yes it's always on and is available when discord-rpc library is found, otherwise it's not available. Let me know if you'd prefer a toggle and failing when the library isn't there |
I was just testing PR.
to confirm that it works on windows
I don't use cmaker. |
The library is always installed, so even if the developer doesn't want discord, it will always be activated. |
Imo should be option with default false. I don't want this enabled in my test build or local one. |
968d52d
to
77612f7
Compare
77612f7
to
14dbe41
Compare
is it finished? |
but
and
compilation is broken (without that compiles correctly)
I’m not used to using CMake; I don’t know if these are the correct steps to enable RPC in CMake |
I'll get a Windows VM and I'll check that. |
Quality Gate passedIssues Measures |
Description
Right now otclient with Discord Rich Presence support can be built with only vc17, not cmake, this PR fixes that.
Since Discord isn't needed for otclient to work and also I don't think OSS projects should depend on proprietary services in any way, let's make it optional, enable it automatically if available during build.
Let me know if a manual switch would be preferred, personally I like it like this.
No idea if this works on macOS/Windows 😕
Behavior
Actual
otclient built using cmake doesn't use Discord Rich Presence
Expected
If discord-rpc is available, enable it in code.
Type of change
Please delete options that are not relevant.
How Has This Been Tested
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Test Configuration:
Checklist