-
Notifications
You must be signed in to change notification settings - Fork 124
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
RCON - use 64 bit time on 32 bit windows systems #719
Conversation
There are no |
35ed5b5
to
590e00d
Compare
590e00d
to
d74a9af
Compare
updated to affect bsd as well, i can confirm this works for the win32 and linux builds, but @VVD hasn't confirmed it fixes the issue with bsd (though i see no reason it shouldn't). |
@VVD , could you confirm that this works now for BSD? |
🤦
If you don't know how to write build system for cross platform projects - just keep it as it was before with gmake. |
Hey @VVD , As we use github as build environment, we tune our build scripts to work on the github ecosystem, and not on a randomly selected distro. I am sorry to hear you frustration that your beloved whateverBSD distro is that special, that is not able to handle the build scripts. |
Just for information (if you don't know): I was the project leader of the mvdsv for 4 or 5 years (~2003-2008) and fixed build system to support everything I have access to - different Linux distros, *BSD, SunOS, MacOS. And now I see how somebody break all this work and got answer "Maybe you should stick to an OS that works". WTF?! freebsd-amd64.cmake:
Why changed in function call, but not changed in implementation?
|
Same with ktx - removed cross platform build, but added What genius wrote this code:
🤦🤦🤦🤦🤦 |
are we still on the subject of the pr here? i don't know what's going on. |
Subject is crypt_rcon is broken. In ezQuake hardcoded size of the string for time:
But in mvdsv it calculated from
Fix is replace |
that's essentially what this pr does except it still uses the size of our time int which is now always uint64, which it should probably also be in mvdsv, that way if we ever change it (say 128?) it's still the one place. |
Move from 32bit to 64bit time_t broke the "protocol" of the crypt_rcon: older clients can't use it with newer mvdsv and newer clients can't use it with older mvdsv. |
correct, that's why we're setting it to something that's always the same size, uint64, that's no different than hardcoding a number |
So your suggestion is to break compatibility with older versions and fixate protocol with 64bit time_t. |
it still won't work on all the current mvdsv servers that are using 64 bit time, which is like 99% of them. may as well just start setting all time on both sides to 64 bit. |
|
if you want to change it again feel free to make a pr for it, i'm fine with leaving it as it fixes 32 bit clients. |
No description provided.