Random Chitchat 2012-2016
The current development branch of your project compiles fine for me under MSVC 2013, after I changed the two #include in Connection.cpp from .cpp to .h.

Remember that you need to re-run "cmake ." every time you add a cpp file to the src folder or when you checkout a different git branch, this is because of how we use cmake "in the wrong way" - we don't list the individual source files, but rather use a file globbing mechanism, which unfortunately means that cmake is unable to auto-detect changes when new files are added or removed, and it needs to be run manually after each such change.
Thanks given by: daniel0916
I'm creating Travis for my project and i become a error.
https://travis-ci.org/daniel0916/MCProxy/jobs/28705919
Do anyone know why this error comes?

I don't know why i have zlib in libraries.. i don't use it...

Edit: Deleted zlib and now gcc is compiling. clang makes an error.. i will fix it.
Thanks given by:
I have found a silly bug in the offline UUID generator code, so the server wasn't able to be run in offline mode, all clients disconnected before logging in. Fixed now.
Thanks given by: daniel0916
I become a error with the StringUtils.cpp:
https://travis-ci.org/daniel0916/MCProxy...22080#L261

Can you help me?
Thanks given by:
StringUtils.cpp doesn't include StringUtils.h but requires it is always included beforehand. Don't know how we got away with that.
Thanks given by:
StringUtils.h is included in Globals.h, so it is included for every cpp file for us.
Thanks given by:
But why comes this error then?
Thanks given by:
Seems like clang is being over-protective. Just disable the error (at the bottom of the SetFlags.cmake file)
Thanks given by:
Where can i disable it in the file?
Should i add a "add_flags_cxx"? And how name do it have?

Edit: I tried it but it isn't working.
https://github.com/daniel0916/MCProxy/co...1bb4044617

Edit2: I fixed it.
https://github.com/daniel0916/MCProxy/co...3712c54db1
Thanks given by:
Its a useful warning. I fixed something like 6 potential security exploits through it. printf is dangerous.
Thanks given by:




Users browsing this thread: 5 Guest(s)