Compiling With Visual Studio.NET

Just an FYI for anyone with an interest. Compiling the code with VC++ in Visual Studio.NET appears to work just fine. You can simply download the code and double-click the VC++ 6 Workspace file. This will launch Visual Studio and give you a popup that says you need to convert the project. Click OK and then build. I did have to tweak the mud.h file and change the path for the AREA_LIST #define and also add the same path to the area files listed in the area.lst file (I'm sure there is a better way, but I'm a newbie). After that, I rebuilt the project and everything seems to be running fine. Best of all, stepping through the code in the debugger works great which was my ultimate objective.

I have visual studio .net 2003, I compiled the source code, it created a set of object files, and symbol files in the debug folder, however there was no executable. I tried running it, the program linked, a command shell popped up for a split second, yet no executable. How do I create an executable out of the object files and such?

If a command shell popped up for a split second, that means that it did indeed make an executable, but the executable died (probably because it couldn't find any of the area files.)

The executable should be in the same directory as the object files, e.g. debug/ in this case. Did you check there after it linked and you got the shell window?

Yea, I got it to work, I downloaded the executable from this site, copied the stuff into my debug folder, and went to my linker settings and set the output path to be my debug folder, thanks for the help ksilyan =)

Whats the website for VC++? :P

if you want documentation on microsoft products, msdn.microsoft.com is an extensive site.

Ninian, could you elaborate what you had to change in mud.h? I too am compiling using VisualStudio.net 2003 and it compiles just fine, but doesn't output a .exe. Thanks!

Make sure your project settings are correct; i.e. that you're compiling an executable. This should be the case.

Also, to be sure, to a search for *.exe from your SMAUG directory - NOT the source directory.

Chances are that if it links with no problem, it's generating an .exe.

Changing the header file won't change at all whether or not an .exe is generated - that's all in the project settings.

OK, now I'm getting this weird error while the project is linking:

Linking...
LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification

I've tweaked all the output folders and went through all the settings...could this warning be messing it up? Any ideas?

That's not an error, it's just a warning... it's telling you that it's not compiling with "edit and continue" debug mode, because it's not linking incrementally.

This won't cause any problems, other than not being able to use edit and continue debug mode. :)

Just a note that vc++ dont put the exe file with the src files it usually puts it by default in c:\source\sumthin well at least my version of it did, it took me a bit of time to work out why when i ran the exe in the \src directory that my changes were not there, a quick search of all my drives located the file. Unless its the project file that has the path imbedded and the exe goes to the path that nick used when making his version of the windows code.

The default with Visual C++ is to normally put release versions in a subdirectory "Release" under the source, and debug versions in a subdirectory "Debug" under the source. Earlier versions used WinRel and WinDebug instead.

However you can change all that in your project settings, so for ease of testing you could just put the executable in the Area folder, and tell the debugger to run from that folder. That is just 2 project setting changes.

Why is there no visual studio project file under the FUSS distributions?

Chances are, because they haven't been tested with VS or do not compile on it due to platform issues.

Start an empty project and add all the .c files to it, and compile. That should largely do it. Follow your nose if you get error messages.

Can anyone explain how to compile Smaug on visual studio.net 2003? I am ok in coding, but far from expert with Visual studio. I create new Win32 console application, then i add in the Solution Explorer all *.c files to Source Files, and all *.h files to Header Files. After that if i just compile or build it, i get " fatal error C1010: unexpected end of file while looking for precompiled header directive" in every *.c file. It seems like i have to change smth in the options, but i dont know what and where.

Check out this link on some info:

http://www.muddomain.com/articles/smaugwin.php

[EDIT] Well that's not exactly what you're looking for it seems, but it's the closest thing I found.

Make sure when you start a new Win32 Command Prompt that you click the "Options" tab in that creation wizard (or whatever the other tab is on that screeen). You need to click the radio buttion (or checkbox, whichever) "Empty project" so it will not try to use any of its ATL, MFC, precompiled header files, etc. in your project.

Err...I can't tell you that smaug compiled with VC++ runs properly. It doesn't support symbols of Russian alphabet :)
But compiled under Cygwin and modified a bit, it does.

Hi guys,

Nice weblink about the VC6 setup Zeno thanks for that..
certainly covered a few other questioned i had about the smaug server as well ..


cheers mate,


Ormuz,