Jump to content
TrinityCore

Joy

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by Joy

  1. I changed

    the file <your_trinitycore_directory/cmake/compiler/xcode/settings.cmake>

    from whatever it was to

    # Set build-directive (used in core to tell which buildtype we used)
    
    add_definitions(-D_BUILD_DIRECTIVE='"$(CONFIGURATION)"')
    
    

    Then it went perfectly well until the XCode links....

    11 errors came up and do not show me the lines:

    Screenshot

  2. Try:

    change the file in <your_trinitycore_directory/cmake/compiler/xcode/settings.cmake>

    from whatever it was to

    # Set build-directive (used in core to tell which buildtype we used)
    
    add_definitions(-D_BUILD_DIRECTIVE='"$(CONFIGURATION)"')
    
    

    And LMAO did you copy the first line from my post ?

  3. Sorry, but it still says "Project "<Directory_of_the_project>" cannot be opened because the project file cannot be parsed"...

    What am I doing wrong ?

    I pull the newest source, Terminal cd-in and mkdir build

    then I cd build, and cmake ../ -GXcode with/without the additional lines from the guide.

    Still generates that error..

  4. I CMade it and opened the project (CMake had no errors) but the XCode popped: "Project "<Directory_of_the_project>" cannot be opened because the project file cannot be parsed"...

    I changed the "TrinityCore/cmake/compiler/xcode/settings.cmake"

    from

    # Set build-directive (used in core to tell which buildtype we used)
    
    add_definitions(-D_BUILD_DIRECTIVE="$(CONFIGURATION)")
    
    
    to
    # Set build-directive (used in core to tell which buildtype we used)
    
    add_definitions(-D_BUILD_DIRECTIVE=\\"$(CONFIGURATION)\\")
    
    

    Was that right?

    *EDIT:

    And when I used git it said: "Fatal: corrupt patch at line 8"

  5. Hi, the file where it builds this information from is automated through CMake, and is as such something that is my responsibility (at least sorting out issues with the buildsystem itself).

    Please try this, and report back to us regarding this - I dont't have a possibility to test XCode myself, so your help will be appreciated.

    diff --git a/cmake/compiler/xcode/settings.cmake b/cmake/compiler/xcode/settings.cmake
    
    index cd33fc1..ad3c58e 100644
    
    --- a/cmake/compiler/xcode/settings.cmake
    
    +++ b/cmake/compiler/xcode/settings.cmake
    
    @@ -1,2 +1,2 @@
    
     # Set build-directive (used in core to tell which buildtype we used)
    
    -add_definitions(-D_BUILD_DIRECTIVE="$(CONFIGURATION)")
    
    +add_definitions(-D_BUILD_DIRECTIVE=\\"$(CONFIGURATION)\\")
    
    

    Thanks for your immediate responsibility !

    But more specifically, how should I apply this ?

  6. Edit By Aokromes:

    If you can't compile check that you meet requirements:

    https://trinitycore.atlassian.net/wiki/spaces/tc/pages/2130068/Requirements

    UVJHm52.png

    If you get SSE2 error use:

    -DCMAKE_C_FLAGS="-msse -msse2 -msse3"
    -DCMAKE_CXX_FLAGS="-msse -msse2 -msse3"

    If you get mysql libs error you miss MySQL development files
    These files are shipped with MySQL Server but to make it easier we packed the libs and include files for both 32 bits and 64 bits.
    Extract the files to a known location, e.g, C:/mysql_libs
    https://github.com/TrinityCore/TrinityCore/releases/download/TDB335.55/mysql_lib.zip

    If you get errorĀ 0xc000007b at start is that you are mixing 32 and 64 bits libraries.

×
×
  • Create New...