-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cmake error #16
Comments
@iMerdjaoui i compile on Linux and Windows - the mistakes that I've had I fixed missing now send to my GitHub! UpdateSent successfully update if you want to test in between my GitHub!I hope the community like! 👊 PS: Forgive me for the mistakes in English - I use the Google translator 😇 |
Closed
does this problem persist on latest revision? |
Yes, sadly. |
@iMerdjaoui Could send the complete log of the error? |
NexusWoW
added a commit
to NexusWoW/azerothcore-wotlk
that referenced
this issue
Jul 31, 2017
These reset entries seem to dictate an entire wipe from encounter from desummoning ads. Trinitycore does not have this and works fine. see trinitycore boss_razuvious. updated DB to represent refreshed entries from trinitycore: -- move understudies to summon groups for proper reset behavior DELETE FROM `creature` WHERE `guid` IN (128184,128185); DELETE FROM `linked_respawn` WHERE `guid` IN (128184,128185); DELETE FROM `creature_summon_groups` WHERE `summonerId`=16061 AND `summonerType`=0; INSERT INTO `creature_summon_groups` (`summonerId`,`summonerType`,`groupId`,`entry`,`position_x`,`position_y`,`position_z`,`orientation`,`summonType`) VALUES (16061,0,1,16803,2757.476,-3111.519,267.7678,3.926991,8), (16061,0,1,16803,2762.049,-3084.467,267.7678,2.129302,8), (16061,0,2,16803,2778.911,-3114.142,267.7678,5.288348,8), (16061,0,2,16803,2781.866,-3088.187,267.7678,0.9075712,8);
Closed
8 tasks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I got this error :
Cmake version : 3.6.0-rc2
Compiling on windows server 2012
The text was updated successfully, but these errors were encountered: