Rochet2

Members
  • Content count

    921
  • Joined

  • Last visited

  • Days Won

    72

Rochet2 last won the day on September 13

Rochet2 had the most liked content!

Community Reputation

191 Excellent

2 Followers

About Rochet2

  • Rank
    Snail
  • Birthday 10/26/93

Contact Methods

  • Website URL
    http://rochet2.github.io/
  • Skype
    Rochet22

Profile Information

  • Gender
    Male
  • Location
    Finland

Recent Profile Visitors

6515 profile views
  1. While the guide isnt perfect, it still captures the most important parts and is good enough for the job. Some of the issues you listed sound like user errors. You are clearly presented a way to create a new user in the mysql installer. If you did not have this view, then you are possibly using some other way of installing MySQL that was unexpected or the installer may have changed over time. https://i.imgur.com/ceQRzfk.png https://i.imgur.com/81Rq8Lz.png You are clearly instructed to leave the subdirectory field empty. Then it will not create a subdirectory. Seems you missed this? https://i.imgur.com/XgRZZjT.png The issue was possibly that you had the wrong boost version installed (did not use the provided links to download or accidentally downloaded wrong version) or that you did not restart CMake between attempting to do things like installing boost and configuring - which is mentioned in the guide. It is also possible that the system variables require a relog in windows or restarting the whole machine to take effect - this is not mentioned in the guide. Without the errors and the state of the machine it is hard to tell afterwards what your issue was. It is possible you installed wrong version of openssl accidentally. Unsure if some unconventional location may also be a reason. Most dependency errors during compile I have seen are caused by users installing wrong dependencies. For example 32 bit library when they compile 64 bit. This mostly happens for MySQL and Boost. Another problem has been the new boost and visual studio versions that required the boost finding script to be changed, but I have not checked if that was corrected already - it may have required some manual fixing. For the issues that you somehow solved it would require seeing the errors and possibly what you have installed and how you have set up the environment to figure out. This is why it is hard to imagine what could have been wrong. Even a small mistake can lead to nothing working and it could be that your system is different in some way from the majority of other systems (new versions of software etc.). So if you cannot solve the problems you should post the error messages and environment data, like what bit version you are compiling, and ask for help. In case you are getting errors there is also a troubleshooting section that has some guides for handling specific errors you may encounter: https://trinitycore.atlassian.net/wiki/spaces/tc/pages/2130044/Troubleshooting+articles In the beginning the guide encourages you to search the forums and ask for help if you cannot find what you need. - There is even a support channel you can ask help live on irc. Anyone is free to edit the wiki, which means that after figuring out what is missing from the guide you can add it in. That being said this software is probably not being built for the average joe to use. Some knowledge about the used software and programming as well as problem solving is likely expected. It should also be expected that a new user will have problems configuring a project of this size and with this many dependencies - even with a perfect guide. New issues keep rising all the time as used libraries and software is being developed by third parties as well as TC.
  2. Take a look at what appveyor does in it's script https://ci.appveyor.com/project/DDuarte/trinitycore/build/1.0.6050 I would recommend using some bash shell, like git bash instead of using windows commandline - windows cli is simply hard to use for anything. Im sure you can google a way to use git bash to get the current version hash from your repo and using that as the output folder should be relatively straight forward. Also you dont need to directly build to a new folder. You can build and then move/rename the build folder or it's contents. Cmake takes some arguments too, which may let you select the build output folder. cmake generates an install project that you can try to build to move the files after buinding them to the cmake configured installation folder.
  3. He says that the issue this thread we are in tries to fix cannot be fixed by using the method described if you downloaded the source as a zip. If you are saying that you can still do this fix, then maybe share some steps? The point is not that you cannot get the version of the zip. The point is that you cannot fix the version showing as Trinitycore rev. 1970-01-01 00:00:00 +0000 on startup and in cmake and everywhere.
  4. If you dont mind updating your core in the process with the fork's TC version that the pull request is made for then you can just do git pull <the fork address> <branch name> If you only want the pull request contents, then you can download it as a diff by appending ".diff" to the end of the pull request URL in github. Same for patch. https://github.com/TrinityCore/TrinityCore/pull/19297 https://github.com/TrinityCore/TrinityCore/pull/19297.diff https://github.com/TrinityCore/TrinityCore/pull/19297.patch The patch would be the same as doing a cherry-pick in a way I guess if you apply it with git am < file.patch There are many other ways to go about doing this. For example you could make a cherry-pick of the commits that are pull requested. (fetch the pull request repository and then do a cherry-pick firstCommitHash^...LastCommitHash) It seems you can also try reference the pull request repository through TC repository as seen here: https://help.github.com/articles/checking-out-pull-requests-locally/ git fetch origin pull/PRID/head:BRANCHNAME origin is assumed to be trinitycore repository.
  5. Its enough to just change the DB names in configs (and in DB hurr durr). I use this all the time to hop through the 5 different core/patch combinations I have. http://i.imgur.com/CPIzrMd.png
  6. Hmm, looks like it does tho: master: https://github.com/TrinityCore/TrinityCore/blob/master/src/server/game/Texts/CreatureTextMgr.h#L234 3.3.5; https://github.com/TrinityCore/TrinityCore/blob/3.3.5/src/server/game/Texts/CreatureTextMgr.h#L241 maybe you should post the error message. You probably have not included Player.h or WorldSession.h or something lke that
  7. https://en.wikipedia.org/wiki/Precompiled_header
  8. You probably downloaded them as zip files instead of using git to download it (clone) The installation guide tells you what you should do. https://trinitycore.atlassian.net/wiki/display/tc/Windows+Core+Installation
  9. They were probably moved to rbac as permissions
  10. Follow the TC requirements page guide on how to install visual studio.
  11. Try delete cache folder in wow installation folder. What patch is this on?
  12. Changed windows guides. Another reference is made here though: https://trinitycore.atlassian.net/wiki/display/tc/OS+X+Core+Installation Btw. this reminded me about this from 2013 http://i.imgur.com/AT3akT0.png
  13. Should change release to RelWithDebInfo in the guide? https://trinitycore.atlassian.net/wiki/display/tc/Windows+Core+Installation
  14. Debug builds contain debug code and run a lot slower. Release is optimized more for actual production. Compile your core with release instead of debug to make it run fast.
  15. If you change things in your source folder (D:/Trinity) then you need to run cmake which will alter the files in the build folder, like the sln file. Also as you build the core many files will likely change inside the build folder, like logs and binary files and so on. But you probably dont want to keep track of the changes cmake does to build folder or the changes compiling makes to build folder or bin folder as those are not "your changes"