VC 6 project files are here -->

EqMule · Post by **EqMule** » Fri May 02, 2003 12:18 pm

ok every single $^%^ post this week has had something to do with compiling, so I decided I cant fight the fire by posting simple step by step tutorials, here is the vc 6 dsp and dsw. I bet this wont be enough though... but here goes -->

1. Copy & Paste this code into a file that you should call MacroQuest.dsp and PLACE it in the 'MacroQuest' folder.

Code: Select all

 # Microsoft Developer Studio Project File - Name="MacroQuest" - Package Owner=<4>
# Microsoft Developer Studio Generated Build File, Format Version 6.00
# ** DO NOT EDIT **

# TARGTYPE "Win32 (x86) Application" 0x0101

CFG=MacroQuest - Win32 Debug
!MESSAGE This is not a valid makefile. To build this project using NMAKE,
!MESSAGE use the Export Makefile command and run
!MESSAGE 
!MESSAGE NMAKE /f "MacroQuest.mak".
!MESSAGE 
!MESSAGE You can specify a configuration when running NMAKE
!MESSAGE by defining the macro CFG on the command line. For example:
!MESSAGE 
!MESSAGE NMAKE /f "MacroQuest.mak" CFG="MacroQuest - Win32 Debug"
!MESSAGE 
!MESSAGE Possible choices for configuration are:
!MESSAGE 
!MESSAGE "MacroQuest - Win32 Release" (based on "Win32 (x86) Application")
!MESSAGE "MacroQuest - Win32 Debug" (based on "Win32 (x86) Application")
!MESSAGE 

# Begin Project
# PROP AllowPerConfigDependencies 0
# PROP Scc_ProjName ""
# PROP Scc_LocalPath ""
CPP=cl.exe
MTL=midl.exe
RSC=rc.exe

!IF  "$(CFG)" == "MacroQuest - Win32 Release"

# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 0
# PROP BASE Output_Dir "Release"
# PROP BASE Intermediate_Dir "Release"
# PROP BASE Target_Dir ""
# PROP Use_MFC 0
# PROP Use_Debug_Libraries 0
# PROP Output_Dir "Release"
# PROP Intermediate_Dir "Release"
# PROP Ignore_Export_Lib 0
# PROP Target_Dir ""
# ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /YX /FD /c
# ADD CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /FR /YX /FD /c
# ADD BASE MTL /nologo /D "NDEBUG" /mktyplib203 /win32
# ADD MTL /nologo /D "NDEBUG" /mktyplib203 /win32
# ADD BASE RSC /l 0x409 /d "NDEBUG"
# ADD RSC /l 0x409 /d "NDEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /machine:I386
# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /machine:I386 /out:"..\Release/MacroQuest.exe"
# SUBTRACT LINK32 /pdb:none

!ELSEIF  "$(CFG)" == "MacroQuest - Win32 Debug"

# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 1
# PROP BASE Output_Dir "Debug"
# PROP BASE Intermediate_Dir "Debug"
# PROP BASE Target_Dir ""
# PROP Use_MFC 0
# PROP Use_Debug_Libraries 1
# PROP Output_Dir "Debug"
# PROP Intermediate_Dir "Debug"
# PROP Target_Dir ""
# ADD BASE CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /D "_MBCS" /YX /FD /GZ /c
# ADD CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /D "_MBCS" /YX /FD /GZ /c
# ADD BASE MTL /nologo /D "_DEBUG" /mktyplib203 /win32
# ADD MTL /nologo /D "_DEBUG" /mktyplib203 /win32
# ADD BASE RSC /l 0x409 /d "_DEBUG"
# ADD RSC /l 0x409 /d "_DEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /debug /machine:I386 /pdbtype:sept
# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /debug /machine:I386 /pdbtype:sept

!ENDIF 

# Begin Target

# Name "MacroQuest - Win32 Release"
# Name "MacroQuest - Win32 Debug"
# Begin Group "Source Files"

# PROP Default_Filter "cpp;c;cxx;rc;def;r;odl;idl;hpj;bat"
# Begin Source File

SOURCE=.\MacroQuest.cpp
# End Source File
# Begin Source File

SOURCE=.\MacroQuest.rc
# End Source File
# End Group
# Begin Group "Header Files"

# PROP Default_Filter "h;hpp;hxx;hm;inl"
# Begin Source File

SOURCE=.\resource.h
# End Source File
# End Group
# Begin Group "Resource Files"

# PROP Default_Filter "ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe"
# Begin Source File

SOURCE=.\EQ.ico
# End Source File
# Begin Source File

SOURCE=.\icon2.ico
# End Source File
# End Group
# End Target
# End Project

2. Copy & Paste this code into a file that you should call MacroQuest.dsw and PLACE it in the root of your sourcefiles i.e in the SAME folder as the MacroQuest.sln file ok!

Code: Select all

 Microsoft Developer Studio Workspace File, Format Version 6.00
# WARNING: DO NOT EDIT OR DELETE THIS WORKSPACE FILE!

###############################################################################

Project: "EQLib"=.\EQLib\EQLib.dsp - Package Owner=<4>

Package=<5>
{{{
}}}

Package=<4>
{{{
}}}

###############################################################################

Project: "MacroQuest"=.\MacroQuest\MacroQuest.dsp - Package Owner=<4>

Package=<5>
{{{
}}}

Package=<4>
{{{
}}}

###############################################################################

Global:

Package=<5>
{{{
}}}

Package=<3>
{{{
}}}

###############################################################################

3. Copy & Paste this code into a file that you should call EqLib.dsp and PLACE it in the Eqlib folder i.e in the SAME folder as the EQLib.cpp file is located.

Code: Select all

 # Microsoft Developer Studio Project File - Name="EQLib" - Package Owner=<4>
# Microsoft Developer Studio Generated Build File, Format Version 6.00
# ** DO NOT EDIT **

# TARGTYPE "Win32 (x86) Console Application" 0x0103

CFG=EQLib - Win32 Debug
!MESSAGE This is not a valid makefile. To build this project using NMAKE,
!MESSAGE use the Export Makefile command and run
!MESSAGE 
!MESSAGE NMAKE /f "EQLib.mak".
!MESSAGE 
!MESSAGE You can specify a configuration when running NMAKE
!MESSAGE by defining the macro CFG on the command line. For example:
!MESSAGE 
!MESSAGE NMAKE /f "EQLib.mak" CFG="EQLib - Win32 Debug"
!MESSAGE 
!MESSAGE Possible choices for configuration are:
!MESSAGE 
!MESSAGE "EQLib - Win32 Release" (based on "Win32 (x86) Console Application")
!MESSAGE "EQLib - Win32 Debug" (based on "Win32 (x86) Console Application")
!MESSAGE 

# Begin Project
# PROP AllowPerConfigDependencies 0
# PROP Scc_ProjName ""
# PROP Scc_LocalPath ""
CPP=cl.exe
RSC=rc.exe

!IF  "$(CFG)" == "EQLib - Win32 Release"

# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 0
# PROP BASE Output_Dir "Release"
# PROP BASE Intermediate_Dir "Release"
# PROP BASE Target_Dir ""
# PROP Use_MFC 0
# PROP Use_Debug_Libraries 0
# PROP Output_Dir "..\Release"
# PROP Intermediate_Dir "Release"
# PROP Ignore_Export_Lib 0
# PROP Target_Dir ""
# ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
# ADD CPP /nologo /W3 /GX /O2 /I "..\dxsdk81\include" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "EQLIB_EXPORTS" /D "CINTERFACE" /YX /FD /c
# ADD BASE RSC /l 0x409 /d "NDEBUG"
# ADD RSC /l 0x409 /d "NDEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /machine:I386
# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib ws2_32.lib /nologo /dll /pdb:"Release/EQLib.pdb" /machine:I386 /implib:"Release/EQLib.lib" /libpath:"..\Detours\lib60"
# SUBTRACT LINK32 /pdb:none

!ELSEIF  "$(CFG)" == "EQLib - Win32 Debug"

# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 1
# PROP BASE Output_Dir "Debug"
# PROP BASE Intermediate_Dir "Debug"
# PROP BASE Target_Dir ""
# PROP Use_MFC 0
# PROP Use_Debug_Libraries 1
# PROP Output_Dir "Debug"
# PROP Intermediate_Dir "Debug"
# PROP Ignore_Export_Lib 0
# PROP Target_Dir ""
# ADD BASE CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /GZ /c
# ADD CPP /nologo /MTd /W3 /Gm /GX /ZI /Od /I "..\dxsdk81\include" /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /D "_MBCS" /D "_USRDLL" /D "EQLIB_EXPORTS" /D "CINTERFACE" /FR /YX /FD /GZ /c
# ADD BASE RSC /l 0x409 /d "_DEBUG"
# ADD RSC /l 0x409 /d "_DEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:console /debug /machine:I386 /pdbtype:sept
# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib ws2_32.lib /nologo /dll /debug /machine:I386 /pdbtype:sept /libpath:"..\Detours\lib60"
# SUBTRACT LINK32 /pdb:none

!ENDIF 

# Begin Target

# Name "EQLib - Win32 Release"
# Name "EQLib - Win32 Debug"
# Begin Source File

SOURCE=.\EQLib.cpp
# End Source File
# End Target
# End Project

4. ok thats it, now just MAKE SURE YOU HAVE VISUAL STUDIO 6 INSTALLED and then go doubleclick the Macroquest.dsw file and you should be able to compile...

now theese files are for people that want more control over their compilation, but for thoose of you who want to make the simplest compile, and no hassle, use nmake ok. here is my step by step tutor on how to download via cvs and compile using nmake --> http://macroquest2.com/phpBB2/viewtopic ... 3826#13826

MQWannaBe · Post by **MQWannaBe** » Fri May 02, 2003 2:30 pm

Does not actually work.

Visual Studio Gives you an error saying the File is Edited and cant be opened as a Workspace.

fwiggles · Post by **fwiggles** » Fri May 02, 2003 6:51 pm

this is a bad idea. I would suggest removing this post. The whole idea for MQ being source only in the first place was so that nt any every day noob can get it. Any resourceful person can DL VC6 and do this. Please remove that post EQmule.

dont_know_at_all · Post by **dont_know_at_all** » Fri May 02, 2003 7:28 pm

These project files are wrong. Use the makefile.

Valerian · Post by **Valerian** » Fri May 02, 2003 10:41 pm

fwiggles wrote:this is a bad idea. I would suggest removing this post. The whole idea for MQ being source only in the first place was so that nt any every day noob can get it. Any resourceful person can DL VC6 and do this. Please remove that post EQmule.

yeah, guess that's a bad idea, should remove the makefile too, and heck, while we're at it, remove the VC7 solution file. after all, any idiot can go out and buy VC7 and compile it... let's make it just plain source code and have everyone try to figure out how to make their own project for it. great idea.

seriously though, CVS confuses enough everyday noobs to make that a good deterrent in itself.

Clawed · Post by **Clawed** » Sat May 03, 2003 12:46 am

Agreed; there's no reason not to have VS6 project files included. CVS is by FAR enough of a deterrent IMO. And anybody with VS7 already has zero trouble compiling this.

EqMule · Post by **EqMule** » Sat May 03, 2003 7:55 am

well In my oppinion NOT having VS6 projectfiles in CVS is lame. I mean, I have access to MSDN through my work, and I can install any and all of the MS developer tools, but I wonder how many ppl can actually do the same easily... and then again, I dont like this approach of trying to "keep the noobs out", we all where noobs at one point or another... hell its open source, its GPLed and thrust me, the very lamest of a noob, will NEVER be able to compile and get a working version even if you give them step by step tutorials or hand them project files because they wont be able to install and configure VS anyway... or even get hold of it... so get over your eliteness and accept this as an attempt to make it easier for people who have an interest in MQ and like myself dont want to use nmake... I needed theese files to be able to debug MQ, to help fix it in the future when it breaks, and just because I can install VS7, it doesnt mean I want to...

All of the Power... None of the Arrogance...

eqjoe · Post by **eqjoe** » Sat May 03, 2003 6:06 pm

I am cool with including the project files. After all, the solution file is included for .NET builds.

I think that we have raised the bar high enough by requiring MQ users to build thier own even though binaries for MQ are already being traded via file sharning programs.

It bytes that some peeps spend more effort posting rather than reading others' posts. And it sucks when the same question gets asked over and over because peeps dont read what is already here.

This is open source after all and if we can cut back on the stupid compiler questions on this broard, I think everyone wins.

When /click is fixed the tradeskill "something for nothing" guys will be back and I am sure they will find a way to exploit MQ and EQ. We have better things to do unless you are really into flaming noobs.

Valerian · Post by **Valerian** » Sat May 03, 2003 6:10 pm

I think most of us are agreed, the CVS needs VC6 project files.

Densetsu · Post by **Densetsu** » Mon May 19, 2003 11:44 am

But flamming noobs is half the fun!
remember that time when I was bathed in gasoline then you guys threw "snaps" at me ? was'nt that fun!? ::shudders:: y-yeah..heh heh..fun.. ::crys::

eq_freak · Post by **eq_freak** » Tue May 20, 2003 10:06 am

Quick reminder:

You can use the below tool to easily convert the .net project files to VS6 format.

http://www.codeproject.com/tools/prjconverter.asp

VC 6 project files are here -->

VC 6 project files are here -->

Im on the noobs side.

Huh?