Compiling problem

A forum for the general posts relating to MacroQuest. *DEPRECATED: This forum is no longer in public use, but remains here for your reading pleasure. Enjoy

Moderator: MacroQuest Developers

Wishbringer
Contributing Member
Contributing Member
Posts: 230
Joined: Thu Nov 14, 2002 7:00 am

Post by Wishbringer » Tue May 27, 2003 2:39 pm

Used TortoiseCVS and had same problem with CR/LF
Checked Preferences/Advanced/Unix_Line_Endings and nothing happened first.
Because CVS don't check CR/LF while updating.
You first have to check Preferences/Advanced/Unix_Line_Endings and THEN you have to do a FRESH checkout (clear whole folder first).

Then all is fine and CR/LF are in the right places. *grin*

compuboy
a ghoul
a ghoul
Posts: 108
Joined: Thu Apr 24, 2003 8:19 am
Location: Good Question, if anyone finds out, let me know

Post by compuboy » Tue May 27, 2003 9:35 pm

*warning* not a CVS power user, more of a noob actually **

I use winCVS (the little yellow fish one) and without changing any options i got it to work like a charm with just the address and such.
ya know, i cant think of anything profound to say here, so....

GO DEVS

woodcraft
orc pawn
orc pawn
Posts: 10
Joined: Tue Jan 14, 2003 10:39 pm

Post by woodcraft » Thu May 29, 2003 4:03 pm

I got the download (again) but I keep getting compile errors "cannot open file wdbgexts.h"

I can't find this file in CVS here - where is it referenced ?

User avatar
dont_know_at_all
Developer
Developer
Posts: 5450
Joined: Sun Dec 01, 2002 4:15 am
Location: Florida, USA
Contact:

Post by dont_know_at_all » Thu May 29, 2003 5:55 pm

That's only referenced by the mqext debug extension. You don't need that to run macroquest.

That file is in your VS installation:
VC98\INCLUDE\wdbgexts.h

woodcraft
orc pawn
orc pawn
Posts: 10
Joined: Tue Jan 14, 2003 10:39 pm

Post by woodcraft » Fri May 30, 2003 9:23 am

I am running VS .net 2003 - the file is not included with it. Can we put it in as part of the CVS repository ?

It is needed as a lot of references exist to use the debug routines.

meep
orc pawn
orc pawn
Posts: 10
Joined: Sun Jan 19, 2003 11:18 am

Post by meep » Fri May 30, 2003 9:30 am

Hmm works fine for me with VS.net Enterprise Architect edition...

Did you install the support libraries?

and run the VS/VC++ environment variables batch file?

User avatar
dont_know_at_all
Developer
Developer
Posts: 5450
Joined: Sun Dec 01, 2002 4:15 am
Location: Florida, USA
Contact:

Post by dont_know_at_all » Fri May 30, 2003 12:47 pm

Vc7/PlatformSDK/Include/WDbgExts.h from VS.NET.

I believe the platform sdk might be available from MS.

woodcraft
orc pawn
orc pawn
Posts: 10
Joined: Tue Jan 14, 2003 10:39 pm

Post by woodcraft » Mon Jun 02, 2003 3:54 pm

I found a listing of the file on the web and copied / installed it. If it is of value, I could send it to someone for inclusion to the CVS archive.

DreamKing
a lesser mummy
a lesser mummy
Posts: 79
Joined: Tue Jun 10, 2003 12:29 am

Post by DreamKing » Fri Oct 10, 2003 1:03 am

I don't have it (wdbgexts.h) as part of my .Net 2003 installation either.

Although I found one in 10 seconds by doing a search. Compiled fine with it (once I edited out line numbers).

http://dotnet.di.unipi.it/Content/sscli ... ource.html

User avatar
dont_know_at_all
Developer
Developer
Posts: 5450
Joined: Sun Dec 01, 2002 4:15 am
Location: Florida, USA
Contact:

Post by dont_know_at_all » Fri Oct 10, 2003 1:16 am

.NET 2003 does not include this file.

I assume that at some time this file will be available with debugger package.

It is now in CVS and will get in the zip at the next update.