Jump to content
TrinityCore

Splattered

Plebs
  • Posts

    7
  • Joined

  • Last visited

Splattered's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. It's not a crash, the log says it can't update the database. The devs would know better than me but I would be checking that you can connect to MySQL using Heidi first. If you can the next step would be make sure you have edited the .conf files with the correct login details to allow the daemon to login to your MySQL DB. Lastly since you mention this is a fresh install, make sure you've created all of the new databases.
  2. I'm not a Mac user so I can't say for certain if the process is the same, similar though I imagine. Basically I exported my databases out of 5.6 - uninstalled 5.6 - installed 5.7 - imported databases - copied new mysql lib files to my Trinity folder - upgraded cmake and VS to the latest - did a fresh compile - copied new auth and world server files to my Trinity folder and fired it up. So far so good.
  3. /facepalm ... guess I'll be doing an upgrade! Thanks for posting your finding
  4. I've also hit this wall. Everything was fine for me until a pull after commit a7636c39d67b17b223952861cc8c6da2725a3a3b. From that point on I started seeing some CXX messages in CMake and the same errors as OP. I'm using Windows Server 2019 Boost 1.72.0 x64 Cmake 3.17.1 x64 MySQL 5.6.47 VS 2019 16.5.3 OpenSSL 1.1.1f x64 I've just run another pull and I'm now at commit 9c9f4d6d20adf7e95ae1a44dc72b6530c3fc0bff. I've cleared out the Build dir and set CMake up again, now CMake is getting an error. CMake Error at cmake/macros/FindMySQL.cmake:237 (message): Could not find the MySQL libraries! Please install the development libraries and headers Call Stack (most recent call first): CMakeLists.txt:70 (find_package) I noticed there is a mention of MySQL 5.6 being deprecated in commit 0fa366cbda66b10584075286db348f0e5e6e8a32. Should we be moving to 5.7?
×
×
  • Create New...