Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ SMAUG
➜ Compiling the server
➜ Compiling With Visual Studio.NET
Compiling With Visual Studio.NET
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
Pages: 1 2
Posted by
| Ninian
(1 post) Bio
|
Date
| Sat 13 Sep 2003 09:32 PM (UTC) |
Message
| 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. | Top |
|
Posted by
| Akumafire
(8 posts) Bio
|
Date
| Reply #1 on Thu 23 Oct 2003 01:46 PM (UTC) |
Message
| 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? | Top |
|
Posted by
| David Haley
USA (3,881 posts) Bio
|
Date
| Reply #2 on Thu 23 Oct 2003 05:19 PM (UTC) |
Message
| 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? |
David Haley aka Ksilyan
Head Programmer,
Legends of the Darkstone
http://david.the-haleys.org | Top |
|
Posted by
| Akumafire
(8 posts) Bio
|
Date
| Reply #3 on Fri 24 Oct 2003 01:07 PM (UTC) Amended on Fri 24 Oct 2003 01:24 PM (UTC) by Akumafire
|
Message
| 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 =) | Top |
|
Posted by
| USER007
(124 posts) Bio
|
Date
| Reply #4 on Fri 24 Oct 2003 11:07 PM (UTC) |
Message
| Whats the website for VC++? :P | Top |
|
Posted by
| Akumafire
(8 posts) Bio
|
Date
| Reply #5 on Sat 25 Oct 2003 12:48 AM (UTC) |
Message
| if you want documentation on microsoft products, msdn.microsoft.com is an extensive site. | Top |
|
Posted by
| Zuccuss
(8 posts) Bio
|
Date
| Reply #6 on Wed 14 Jan 2004 02:37 PM (UTC) |
Message
| 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! | Top |
|
Posted by
| David Haley
USA (3,881 posts) Bio
|
Date
| Reply #7 on Wed 14 Jan 2004 03:27 PM (UTC) |
Message
| 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. |
David Haley aka Ksilyan
Head Programmer,
Legends of the Darkstone
http://david.the-haleys.org | Top |
|
Posted by
| Zuccuss
(8 posts) Bio
|
Date
| Reply #8 on Thu 15 Jan 2004 03:11 AM (UTC) |
Message
| 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? | Top |
|
Posted by
| David Haley
USA (3,881 posts) Bio
|
Date
| Reply #9 on Thu 15 Jan 2004 03:13 AM (UTC) |
Message
| 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. :) |
David Haley aka Ksilyan
Head Programmer,
Legends of the Darkstone
http://david.the-haleys.org | Top |
|
Posted by
| Robert Powell
Australia (367 posts) Bio
|
Date
| Reply #10 on Thu 15 Jan 2004 09:29 AM (UTC) Amended on Thu 15 Jan 2004 09:30 AM (UTC) by Robert Powell
|
Message
| 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. |
Just a guy having a bit of fun. Nothing more, nothing less, I do not need I WIN to feel validated. | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #11 on Thu 15 Jan 2004 07:51 PM (UTC) |
Message
| 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. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
Posted by
| Jeryx
(7 posts) Bio
|
Date
| Reply #12 on Mon 04 Oct 2004 03:00 PM (UTC) Amended on Mon 04 Oct 2004 03:54 PM (UTC) by Jeryx
|
Message
| Why is there no visual studio project file under the FUSS distributions? | Top |
|
Posted by
| David Haley
USA (3,881 posts) Bio
|
Date
| Reply #13 on Mon 04 Oct 2004 04:43 PM (UTC) |
Message
| Chances are, because they haven't been tested with VS or do not compile on it due to platform issues. |
David Haley aka Ksilyan
Head Programmer,
Legends of the Darkstone
http://david.the-haleys.org | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #14 on Wed 06 Oct 2004 06:51 AM (UTC) |
Message
| 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. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
61,676 views.
This is page 1, subject is 2 pages long: 1 2
It is now over 60 days since the last post. This thread is closed.
Refresh page
top