We now have this successfully running using FiveWin Harbour ( 11.11 ), Microsoft Visual Studio 2010 ( VC ), and Harbour 3.0. To do this, when you configure your compiler, use the Harbour config ( its included in your FWH distribution if its not already on your system ) and make sure it is setup as follows:
- Code: Select all Expand view RUN
# --------- Harbour y FWH configuration --------
# --- general --------------------------------------
# $P - project name
# $Pp - path to project directory
# $Pn - project name
# --- compile --------------------------------------
# $I - input full name
# $Ip - input path
# $In - input name
# $Ie - input extension
# $O - output file
# $Op - path to output file
# $On - output filename (without path)
# $Oe - output extension
# $R - release/debug setting for compiler
# --- build ----------------------------------------
# $T - target full name
# $Tp - target path
# $Tn - target name
# $O - output file
# $Op - path to output file
# $On - output filename (without path)
# $Oe - output extension
# $R - release/debug setting for linker
[Settings]
Target =
Category&01 = DEFAULT RUN CONFIGURATION
Working Directory =.
Command Line Arguments =
Category&02 = Harbour Options
Automatic Memvar Declaration = no|yes
Variables Are Assumed = no|yes
Generate Preprocessed Output = no|yes
Warning Level = 1|2|3|4|0
User Include Path =
User Defines =
Compiler Options =
Linker Options =
Excluded Files = Excludes
[SettingsInfo]
Target = Provides a space for you to specify an output file and location of the program that the linker creates.
Working Directory = Provides a space for you to specify the directory in which executing occurs. If you do not specify a directory, executing occurs in the directory where the executable is located.
Command Line Arguments = Provides a space for you to specify command-line arguments you want to pass to the program at startup.
Compiler Options = Provides a space for you to specify an additional compiler options.
User Defines = Shows the switches the tool will use to build. Use ';' as delimiter.
Linker Options = Provides a space for you to specify an additional linker options.
Excluded Files = This will exclude the file(s) included in this UE project group from the build.
[SettingsReps]
User Defines = @[;|-D%s]
Automatic Memvar Declaration = no=|yes=/a
Variables Are Assumed = no=|yes=/v
Generate Preprocessed Output = no=|yes=/p
User Include Path = ^^@[;|;%s]
User Include Path&1 = ^^@[;| /i%s]
Use Multi Thread Library = no|yes
Warning Level = @/w%s
[Variables]
FWH = L:\fwh
HPATH = L:\Harbour
CPATH = c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC
SDKPATH = c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A
FPATHL = $(FWH)\LIB
HPATHL = $(HPATH)\LIB\WIN\MSVC
CPATHL = $(CPATH)\LIB
SDKPATHL = $(SDKPATH)\Lib
UPATHL = L:\Harbour\UserLibs
HOPT = /n /gc0 /q0 $(Compiler Options) /i$(HPATH)\INCLUDE /i$(FWH)\INCLUDE $(User Include Path&1) $(User Defines) $(Automatic Memvar Declaration) $(Variables Are Assumed) $(Generate Preprocessed Output) $(Warning Level)
COPT = -TP -W3 -c -I"$(CPATH)\INCLUDE"
LOPT = /nologo /subsystem:windows /force:multiple /NODEFAULTLIB:libc
# Five Win libraries
LIBS1 = FiveHC32.lib FiveH32.lib
# Harbour Libraries
LIBS2 = hbrtl.lib hbvm.lib gtgui.lib gtwin.lib hblang.lib hbmacro.lib hbrdd.lib rddntx.lib rddcdx.lib rddfpt.lib hbsix.lib
LIBS3 = hbdebug.lib hbcommon.lib hbpp.lib hbwin.lib hbcpage.lib hbct.lib xhb.lib hbpcre.lib png.lib hbzlib.lib
# VC libraries
LIBS4 = kernel32.lib user32.lib gdi32.lib winspool.lib comctl32.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib oledlg.lib winmm.lib
LIBS5 = uuid.lib odbc32.lib odbccp32.lib iphlpapi.lib mpr.lib version.lib wsock32.lib psapi.lib msimg32.lib libcmt.lib oldnames.lib libcpmt.lib
# 3rd Party libraries
LIBS6 = [i][b]add any user libs here[/b][/i]
LIBS = $(LIBS1) $(LIBS2) $(LIBS3) $(LIBS4) $(LIBS5) $(LIBS6)
[Environment]
PATH = $(HPATH)\BIN;$(CPATH)\BIN;%PATH%
INCLUDE = $(FWH)\INCLUDE;$(HPATH)\INCLUDE;$(CPATH)\INCLUDE;$(SDKPATH)\INCLUDE
LIB = $(FPATHL);$(HPATHL);$(CPATHL);$(SDKPATHL);$(UPATHL)
BuildMode = %UESMode%
[General]
TargetExt = .EXE
ReleaseOut = Release
DebugOut = Debug
UseFullPaths = 1
UseDosNames = 0
Excludes = $(Excluded Files)
GenerateEDGroup=$(External Dependencies)
.CPP = .C
[MakeCommands]
run = Execute Application
makef = Show Makefile
[Execute Application]
Title = Execute $T
Cmd0 = $(Command Line Arguments)
Depends = $T
ShowWindow = 1
DisplayConsole = 0
[Show Makefile]
Title=Show makefile
Cmd0=uestudio makefile
ShowWindow=0
DisplayConsole=0
[InsertFiles]
[FileGroups]
FGO = .obj;
FGR = .res;
FGL = .lib;
FGD = .def;
[GroupFormats]
FGO = %s
FGR = %s
FGL = %s
[Build]
Out = $T
Depends = $FGO $FGR
DebugFlag =
ReleaseFlag =
Cmd0 = LINK $(LOPT) $FGO [i][b]yourfile[/b][/i].res $(LIBS)
[.PRG]
Out = $In.c
DebugFlag = /b
ReleaseFlag = /l
Cmd0 = harbour $I $(HOPT) $R /o$O
IncFiles = 1
CaseSensitive = 0
IncDirs = .;$(INCLUDE);
IncKeyWords = #include;
Comments = /*.*/.//.eol.
[.C]
Out = $In.obj
Cmd0 = cl.exe $(COPT) $I
[.RC]
Out = $In.res
Cmd0 = L:\vc98\bin\rc.exe -r -fo$O $I
IncFiles = 1
CaseSensitive = 0
IncDirs = .;$(INCLUDE);
IncKeyWords = #include;
Comments = /*.*/.//.eol.
Please note the following:
[list=]
Your path names may be different
We use an rc compiler from VC98, an older version of Visual C. You should substitute the name/path for your own resource compiler
Be sure to add any additional user libraries
The .prg files are not mentioned here. They will include all .prg files you define in the Project automatically. Also include your rc files in the project list.
[/list]
My special thanks to Antonio and Daniel who were very helpful in this process. I felt this was important because 1) many people told me how good UE Studio is, and that I should be using it, 2) Its much easier then maintaining a make file, 3) I really believe we will prosper more if we are fully compatible with Microsoft C compiler, and use the latest versions. On this last point, you can use Visual C 2010 Express, available for free from Microsoft. Soon we will have the 2012 versions, Windows 8, Metro, windows tablets ( to work with the Windows 7 phone which is gaining popularity ), servers, cloud services, etc. all available to us.
Tim
