Macroquest2-VS2012.sln missing

[zombie sid]

Macroquest2-VS2012.sln missing from update March 16, 2016

Usually when I download I just click on the VS2012 version, easy ...

Guess I need to do it the old fashioned way... hope I remember and it works

[demonstar55]

MQ2 has been upgraded to require a minimum version of 2013 (I would recommend VS2015 community edition, multiple VS installs live very nicely together if you still require a specific version for whatever reason) and the multiple sln files has been done away with.

[EqMule]

As per changes.txt we only distribute ONE solution file from now on to make building MQ2 easier and not confuse people and it's: MacroQuest2.sln

09 Mar 2016
- Updated for TEST
- New SPA's added
- IsBodyType has been renamed to HasProperty (cause thats what it is)
- Bunch of changes to mq2windows, lets see if it works as intended.
-
- Added a new TLO Member to ${Me} .AssistComplete
. You can check it after you do a /assist. It will be true when the assist request has been completed.
. Usage Example:

Code: Select all

    /assist Eqmule
    /delay 5s ${Me.AssistComplete}==TRUE
    /if (${Target.ID}) {
        /echo EqMule wants me to help fighting ${Target}
    }

- Turned on Exception Handling (/EHsc) for all projects except mq2main
- when we move to the v140xp toolset we can use the noexcept keyword to turn it on for mq2main as well...
-
- --------------------> VERY IMPORTANT STUFF BEGIN <-------------------
- It's time to upgrade to Visual Studio 2013 Community or newer.
- From this version and onward we will not support older compilers.
- There just isn't any good reason now that Microsoft has free Community Editions
- which can build mq2 just fine.
- Therefor:
- All vcxproj files has been updated to use the vs2013 toolset (v120xp) (thanks Brainiac)
- We want to move to 2015, but we will have to wait until ISXDK supports that version.
- If you use 2015, just install the vs 2013 community edition if you want to build ISXEQ
- For mq2 it doesn't really matter, you can build it with 2015 toolset (v140 or v140xp)
- just let it upgrade if it asks for it.
-
- Older solution files has been removed:
- For building MQ2 use MacroQuest2.sln
- --------------------> VERY IMPORTANT STUFF END <---------------------
-
- If you have no interest in building ISXEQ you can stop reading now.
-
- For building ISXEQ use ISXEQ.sln PLEASE NOTE: --------------->
- The red headed stepchild ISXEQ has gotten some love this week.
- You might have noticed that the zip grew a bit in size this release
- the reason is that it now includes all files needed to build ISXEQ.
- So...
- This means that from now on, you can just open ISXEQ.sln and build it.
- DO NOT LET IT UPGRADE THE TOOLSET! it only works with the v120xp toolset.
- Having said that, No more additional downloads, googling for libs, headers, updating paths
- patching files, reading pages and pages of forum threads, and all that extra
- shiz that we all love to spend time on...
- In other words we made it easier to build ISXEQ "out of the box" (aka the zip)

[zombie sid]

Thank you ... my bad

appreciate the explanation

[warlock45]

Just to toss this out there for folks struggling

This was one of the oddest compiles I have done in a while. I use VS2015 and this compile required I install some windowXp C++ (if I read the VS pop up window correctly), reboot (cause of course , its microsoft....) of course a VS upgrade... then for some reason had to manually re-target 7 plugins to get the vcproject files loaded (huh?) logged in game to get a message that 2 of the plugins I just compiled were out of date (double huh?) so, logged out to recompile the whole solution again.

sometimes it seems like a whole week of mondays.... heh.

[demonstar55]

You can select all the projects and edit them en-masse. The projects are set up for VS2013 by default, so if you don't have 2013 installed as well, you have to retarget them for 2015.

[warlock45]

aye, I do that right off everytime. Why I found it odd that it highlighted specific plugins with error messages and told me to retarget them. Would not let me do it through the solution, but rather each plugin, for some reason.

Same as rebuilding the solution for some reason missed 2 plugins (despite showing them rebuilt) but... rebuilding the solution again got them... weirdness all around =)