Jump to content
TrinityCore

Kretol

Members
  • Posts

    27
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Kretol

  1. On 6/2/2017 at 8:43 AM, CDawg said:

    Actually, it can get goofy and you do have to set the path manually for Linux users. (similar to Windows)

    I did have to export BOOST_ROOT=$HOME/boost_1_63_0. (idk, maybe it was me when I upgraded my boost :P )

    Fortunately for Linux users that CMake has a catch all process before compiling and finding out before you get half way into compiling your core and not spewing errors. I think there is a specific Boost version install that doesn't set within the registry correctly for Win users or If you install, reinstall, something gets goofy with Win users.

    Edit:

    Oh btw, when I remove the old boost directories, I get errors during the cmake process, even though it's looking at the newer version boost.

    An example: I have 3 directories boost_61/ boost_62/ and boost_63/, however when I remove 61 and 62 (old ones) cmake says it's using boost_63, but during the compile i still get 'cant find boost libraries'

    So I place them both back (61 and 62) and everything is fine. ¯\_(ツ)_/¯

    It's quite frustrating.

    I recently updated to 1_64 from 1_60 and had the exact same issue (Windows).  However, I had purged the Recycle Bin so couldn't restore the folder.  After a bit of searching and checking the directory structure, I noticed that the lib directory was named lib64-msvc-14.1, so I renamed it to just lib and then it worked fine! :)

×
×
  • Create New...