Jump to content

Pysis

Members
  • Posts

    30
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    0.00 GBP 

Pysis last won the day on June 17 2020

Pysis had the most liked content!

Core Infomation

  • Core
    Zero

Contact Methods

  • Discord
    Pysis#1215

Recent Profile Visitors

368 profile views

Pysis's Achievements

Advanced Member

Advanced Member (3/3)

2

Reputation

1

Community Answers

  1. Sample CMake/Generate command: Sample, optional, non-string CMake parameters: Sample VS build command:
  2. Krill — 02/21/2021 https://github.com/MangosServer/MangosSharp https://github.com/mangosvb/DatabaseZero Run install batch files and setup DB, setup realmserver in auth db like normal Perform any needed updates found here: https://github.com/MangosServer/MangosSharp/tree/main/SQL Open M# .sln here: https://github.com/MangosServer/MangosSharp/tree/main/Source And build all projects (around 30). Extract data using Mangos.Extractor & Mangos.DBCExtractor tools here: https://github.com/MangosServer/MangosSharp/tree/main/Source/Tools Setup RealmServer, WorldCluster, WorldServer configs and start servers via the RunServers batch file. DB is not the same (2014, very outdated). The source itself needs updating to use DB updates, but the plan is for it to use latest. Another thing, you will need https://dotnet.microsoft.com/download/dotnet/5.0 for it to run and compile.
  3. I thought this would be the best place to chronicle some of the building woes I had and how to solve them, instead of on the "Installing Cmake" and "Installing Visual Studio 2015 (Community)" pages. "Installing Mangos on Windows (Manually for Zero, One and Two)" was another idea, but this page seemed to be more visited, but also similar in process with simpler user flow, common tools, etc., so I'll just leave it here for now. It all started when I had a working process, but then decided to use latest CMake 3.20. When I did this, at least through Easy Build, I had the following error: After that, I would continue the successive attempts by running the "cmake.cmd" file in the root of a server core's source code, I think generated by EasyBuild. I then tried CMake 3.4 like I thought I had on my system from a while ago, but I must not have actually used it recently because it failed with: Which is detailed in the "CMakeLists.txt" file as the minimum required. With that version I received the errors I was trying to compile for the latest Visual studio VS2019, which could be a bit contradictory as I can explain later, but I thought to use a newer version of CMake. Maybe I had actually used 3.18 before as I looked in another core's build directory that I had on my drive, but can't remember how I chose that version exactly. Now with that version I received this error: Very strange, as the parameters all looked correct to me. It did work in the CMake GUI, but I wanted to see how it formed that CLI string. It seemed that log pane included all the usual log messages except for the very first and last, the former which I was more curious about. The first error I found when actually generating file results was that it placed them in the same source directory, which is not typical. I wanted to check why Easy Build seemed to generate the cmd file this way, but it started failing for whatever reason with this error: My guess is how my PATH may have changed, but every time I installed a new CMake version, I made sure that options was disabled. Going into Windows I confirmed I only had one entry there, for the default installation which was the 3.20 version currently. This was with EasyBuild version 2.2.6. Without that to help compare, I continued. Now from this point I modified the build path with a suffix of "_build". Seemed straight forward, but then I ran into either of these errors: I think I got the first error immediately, then I tried specifying the source directory with "-S" instead of it simply being positional, in order to get the second. After some frustrations and random attempts, possibly from looking at the "--help" doc and seeing the main/common argument descriptors, I found that if I substituted "--build" for "-B", it finally worked! After seeing this, it may help the problem I found with CMake 3.20 as well, and if so, would require an update to the EB program too. I encountered these troubles once revisiting the project after several months, trying to help a user figure out why they were not getting any "_install" folder results. I suspected some recent refactorings and user error concerning "USE_STORMLIB:BOOL=1" were being used incorrectly and were necessary, but that was less likely because in addition to trying CMake, maybe both automated and manual attempts with the GUI and not I am guessing, the user was also using EasyBuild where they said it similarly failed, although it is important to remember for later troubleshooting as it may be incorrectly mentioned in all or some details. I am still waiting for confirmation, but what I believe was the problem seems to be the user choosing the "ALL_BUILD.vcxproj" file to build, when really I think it should be the "MaNGOS.sln" file. I actually tried to replicate their issue similarly, but when I started my VS2019 program, it found the entire solution anyway, built, and packaged all of the files correctly! So with all of that I thought I could also attach some sample log files to show how each large part of the process proceeded that I don't think you will already find enough detail here for, in case people want to link to and search through it for keywords, path and environment comparisons, etc. MaNGOS CMake Example.txt MaNGOS Build Example.txt
  4. Since updates, my other comments here, and my own recent success, I should report that Visual Studio 2019 Community Edition, version 16.9.2, EasyBuild version 2.2.6, and CMake version 3.18, all on Windows 10 Pro 64-bit, I was able to build a MaNGOS core successfully, thanks to the great work of others! The VS minor and patch versions were both very important to keep updated throughout, but may hopefully be less important now.
  5. It may be just simple to compile the project yourself instead of following anything else explicitly. I want the getmangos.sh script to take care of everything for Linux OSes at least, but I always hear it's in a state of repair. More notes: From the guide you link: "You also need to grab and compile libace. You can get it from here. Extract it and read the instructions.They're pretty straight-forward. It should be named 'ACE-INSTALL.html' or something similar. https://download.dre.vanderbilt.edu/ ACE https://www.dre.vanderbilt.edu/~schmidt/ACE.html Maybe you can find a download from that link, but instead I looked through the GitHub repository: https://github.com/mangosone/server Following deps I see acelite, and since it is bundled with the Mangos source code, I think it's important to use that version specifically. That leads to this linked module repo and directory, where I did find that "ACE-INSTALL.html" file: https://github.com/mangos/mangosDeps/tree/1228d504656d73a3a7eaf1fe5e2b594c9e48a8a0/acelite I think UNIX build instructions would make the most sense from that list, since it does not have "Linux", and GNU Make/Configure is pretty common for Linux packages. I was hoping for an existing Ace(Lite) package in the Debian repos but did not see anything quickly from here: https://packages.debian.org/search?keywords=ace&searchon=names&suite=stable&section=all Those usually have scripts that aid with compiling yourself automatically.
  6. Pysis

    Installing MySQL 5.7

    For using MySQL 8.0, all I had to do so far was update the password scheme for the database connection user(s). Working so far with minimal testing, you just need to run this SQL: The default was the caching_sha2_password scheme.
  7. I was going to reply but the process was long running. I saw that the issue was the linux package as she seems to realize now. I just following this guide for Windows which uses the Linux-style script and the more obvious Windows binaries: https://www.getmangos.eu/wiki/documentation/installation-guides/guideswindows/extracting-game-data-r20067/ That should help, and also I can report there is no current large issues with the three's client extraction tools. I can post my log and some details for reference as attachments. I have the result folders with files in them as you can see below, and some errors during the process as well. My tools directory for Mangos Server Three that I compiled from source on master at 18d218a2ae23ecc91b673cb163be4bc9ffe7e897 just yesterday in Release mode, but the release package should work too: My result folders with some meaningful information: MaNGOSExtractor.log MaNGOSExtractor_detailed.log MoveMapGen_detailed.log
  8. When he said latest patch like 1.12.1 for Zero then it seems not without personal effort.
  9. Pysis

    Installing MySQL 5.7

    Those minor revisions are just patch releases to fix bugs or security issues, use the latest. AntzToday at 6:02 AM @Whyarp 5.7 is the ideal version, but we have done a lot of work recently to support 8.0 (not 100% tested though) [6:03 AM] of the 5.7.x versions, just grab the latest(edited) Ryan WadeToday at 6:03 AM Thank you Antz, much appreciated! Elmsroth [FR]Today at 7:03 AM @Whyarp Be careful with 5.7, with some DB script it could block the execution of DB import because of the SQL_MODE (you should set SQL_MODE as an empty string otherwise it could lead to errors).(edited) [7:03 AM] Sometimes related to Zero dates instead of 1900-01-01 - 00:00:00 [7:04 AM] If I remember well [7:04 AM] https://dev.mysql.com/doc/refman/5.7/en/faqs-sql-modes.html
  10. That's a lot of dots... "I am trying to setup zero using the getmangos.sh script." So that would be a fresh install. Guides have you do: I took the script from here:, which I found on the CentOS 7 install guide: https://raw.githubusercontent.com/mangoszero/server/master/linux/getmangos.sh Edited Wednesday at 10:08 AM by Mac Wheeler Now, we can download our installer: wget https://raw.githubusercontent.com/mangoszero/server/master/linux/getmangos.sh Set the permissions to be allowed to execute it: chmod 700 getmangos.sh And execute it: ./getmangos.sh That doesn't have him doing any git, at least for now..
  11. but getmangos is a contain all script, the guides tell you to just download that script directly, individually, and it does the rest?
  12. He shouldn't need that command though, you are just mentioned that's what the script does now?
  13. From the community help forum by Mac Wheeler, ported to here from The advice given to Mac should be checked that the script is following as well, checking out the git repo completely/recursively with all submodules and their contents properly downloaded.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use