UE Studio / FWH / xHarbour / MS compiler

[TimStone]

This topic has been around before ... but I wanted to get some "current" input.

I'm using UE Studio 11.0 ( just released )
FWH 11.xx ( currently .03 until the .04 problems are solved )

I currently build with xBuilder ( xHarbour.com.) However, I have access to xHarbour ( Microsoft ) with the FWH subscription. ( NO, I don't want to use Borland ... BTDT ... not going there ). I also have Visual Studio 2010 installed, so I do have the Microsoft compilers.

Has anyone configured UE Studio to build applications using these tools ? If so, can you provide specific guidelines for setting it up properly ?

Thank you.

[TimStone]

Is no one using this combination ?

[Antonio Linares]

Tim,

In FWH there is a UEStudio folder where you have the configs\Harbour\Application file. Just edit it and modify it using the compiler and libs info from FWH\samples\buildhm.bat

[TimStone]

I am working with that but still having a problem..

I think several of us would love to use the full power of UE Studio but documentation is a problem. I'm not quite sure how much of the compiler setup I need to add, and how much is done by default.

That is why I was wondering if anyone has actually setup a Project in UE Studio that builds an application with FWH using Microsoft Visual Studio Visual C ?

Last year we had a long discussion on this and the use of Borland. However, to bridge the gap and "do what we need to do" this decade, we will benefit more from Microosft C then Borland ( 64 bit, mobile apps, etc supported by Microsoft but not Borland as you pointed out last year in your helpful comparison ). Also, that may open the door to bridge the gap between FWH and .NET. Many times I asked questions on xHarbour forums and the response was "that is not supported by Pelles C".

As I study Visual Studio, there are many powerful capabilities that do not need to be duplicated in FWH ( thats way too much work ), but we might benefit by merging the best of both worlds.

So ... if anyone uses Visual Studio ( 2008 or 2010 ) to build an app with FWH and xHarbour ( Microsoft - from the FWH site ), and you have the compiler setup, I'd sure appreciate seeing it ! Thanks.

[Antonio Linares]

Tim,

These are the settings for FWH 64 bits and Harbour. You just need to change the VC libs names based on buildhm.bat

UEStudio/Configs/Harbour/Application_64

Code: Select all  Expand view

# --------- 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 = c:\fwteam
HPATH = c:\Harbour
CPATH = c:\vc64

HPATHL = $(HPATH)\LIB\vc64
CPATHL = $(CPATH)\LIB

HOPT = /n /gc0 /q $(Compiler Options) /i$(HPATH)\INCLUDE $(User Include Path&1) $(User Defines) $(Automatic Memvar Declaration) $(Variables Are Assumed) $(Generate Preprocessed Output) $(Warning Level)
COPT = -TP -W3 -c -I$(HPATH)\INCLUDE

LOPT = /nologo /subsystem:windows /force:multiple /NODEFAULTLIB:libc
LIBS1 = $(FWH)\LIB\FiveH64.lib $(FWH)\LIB\FiveHC64.lib
LIBS2 =  $(HPATHL)\hbrtl.lib $(HPATHL)\hbvm.lib $(HPATHL)\gtgui.lib $(HPATHL)\hblang.lib $(HPATHL)\hbmacro.lib $(HPATHL)\hbrdd.lib $(HPATHL)\rddntx.lib $(HPATHL)\rddcdx.lib $(HPATHL)\rddfpt.lib $(HPATHL)\hbsix.lib $(HPATHL)\hbdebug.lib $(HPATHL)\hbcommon.lib $(HPATHL)\hbpp.lib $(HPATHL)\hbcpage.lib $(HPATHL)\hbwin.lib
LIBS3 = $(CPATHL)\kernel32.lib $(CPATHL)\user32.lib $(CPATHL)\gdi32.lib $(CPATHL)\winspool.lib $(CPATHL)\comctl32.lib $(CPATHL)\comdlg32.lib $(CPATHL)\advapi32.lib $(CPATHL)\advapi32.lib $(CPATHL)\shell32.lib $(CPATHL)\ole32.lib $(CPATHL)\oleaut32.lib $(CPATHL)\uuid.lib $(CPATHL)\odbc32.lib $(CPATHL)\odbccp32.lib $(CPATHL)\iphlpapi.lib $(CPATHL)\mpr.lib $(CPATHL)\version.lib $(CPATHL)\wsock32.lib $(CPATHL)\msimg32.lib $(CPATHL)\oledlg.lib
LIBS = $(LIBS1) $(LIBS2) $(LIBS3)

[Environment]
PATH = $(HPATH)\BIN;$(CPATH)\BIN;%PATH%
INCLUDE = $(HPATH)\INCLUDE;$(CPATH)\INCLUDE;$(FWH)\INCLUDE
LIB = $(HPATH)\LIB;$(CPATH)\LIB
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 = $(DCon)

[Show Makefile]
Title=Show makefile
Cmd0=uestudio makefile
ShowWindow=1
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 $(LIBS) $FGR

[.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) -o$O $I

[.RC]
Out = $In.res
Cmd0 = rc -r -fo$O $I

IncFiles = 1
CaseSensitive = 0
IncDirs = .;$(INCLUDE);
IncKeyWords = #include;
Comments = /*.*/.//.eol.
 

UEStudio/projects/Harbour/window_64.wiz

Code: Select all  Expand view

##############################################################################
#                                                                            #
#             UEStudio's User Defined Project Template                       #
#                                                                            #
# The following template is to be modified by the user.  It describes        #
# individual preferences for new project creation.                           #
#                                                                            #
# The first and most important section is [UDT] which contains a "Compiler"  #
# variable and a list of seed files to be inserted in the newly created      #
# project.  The Compiler variable specifies the name of the compiler's       #
# configuration directory, and the compiler configuration file.              #
# For example:                                                               #
# Compiler = Microsoft Visual C++ Compiler\Win32 Console Application         #
#                                                                            #
# The list of project files may be any combination of source, header,        #
# resource, and data files.  An example follows:                             #
#  File0=MyApp.h                                                             #
#  File1=MyApp.c, Source Files                                               #
#  File2=MyApp.ico                                                           #
# and so forth....                                                           #
#                                                                            #
# All subsequent section(s) of this template describe the contents of one    #
# or more of the project files defined above.  An optional group name may    #
# be specified after the file name.  In the above example, the group         #
# "Source Files" will automatically be created and MyApp.c will be included  #
# in the group folder.                                                       #
#                                                                            #
# For binary file contents such as Resource, Icon, or any other data file,   #
# where it is inconvenient to describe the contents in a script, the         #
# following format may be used:                                              #
# [File2]                                                                    #
# INCLUDEBINARY=c:\my_data_files\ico_data.raw                                #
# This will create [File2], in this case "MyApp.ico", with the content       #
# ico_data.raw                                                               #
#                                                                            #
# Alternately, binary file contents may be defined in this template using    #
# the ":HEX" directive.  This specifies that all data is represented as      #
# hexadecimal values.  For example:                                          #
# [File3:HEX]                                                                #
# 0065 66 F0, 0FF0, 0F0F0F0F                                                 #
# 12, FF, 20; 0F 40                                                          #
#                                                                            #
# where all numbers above are interpreted based on data length, as follows:  #
#  1-2 = bytes, 3-4 = words, 5-8 = dwords, >8 = an array of bytes.           #
#                                                                            #
# Predefined variables may be used to specify the names of files as well as  #
# the content of the files, e.g.:                                            #
# USER (user name), COMPUTER (computer name), TIME, DATE, PRJPATH (project   #
# path), PRJNAME (project name), PRJDIR (project directory)                  #
# Example: File0=$(PRJNAME).cpp                                              #
#                                                                            #
##############################################################################

[UDT]

Compiler = Harbour\Application_64

File0 = $(PRJNAME).prg
File1 = $(PRJNAME).rc

[File0]
#include "FiveWin.ch"

function Main()

   local oWnd
   
   DEFINE WINDOW oWnd TITLE "Test"
   
   ACTIVATE WINDOW oWnd
   
return nil

[File1]
#include <winapi.ch>

[TimStone]

Setting aside UE Studio, is anyone using a current ( 2010 ) version of VC Microsoft to build their applications ?

I've been trying but experiencing issues ... the latest is that Visual Studio 2010 no longer provides an rc.exe !

I'm sure I'll get lots of "try Borland" but we do actually need to build this bridge to use Microsoft current compilers to build our products ... it will benefit us in the long run.

So, I'd love to see a working .mak file using Microsoft VC 2010 to actually build a full application.

Thanks.

[Antonio Linares]

Tim,

I am just installing msvc 2010 express...

[TimStone]

I may have an interesting finding on this. In the MSDN it states that CL cannot be run from the command line ( as UE is trying to do it ) after 2005. Also, the RC compiler is not provided. These are changes to the program.

Let me know if you can go beyond that note, but my setup builds the ppo and the .c file, but not the obj which would mean cl is not running.

Of course, if someone has a working Makefile with VC 2010 it would mean what I saw is not accurate ...

[Antonio Linares]

Tim,

cl.exe is running fine

I am building it right now and then I will post the required steps and make files

[Antonio Linares]

Tim,

It is working fine (using Harbour, not xHarbour)

To build Harbour 32 bits with Microsoft msvc 2010 express:
viewtopic.php?p=115499#p115499

uestudio\configs\Harbour\Application_vc32

Code: Select all  Expand view

# --------- 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 = c:\fwteam
HPATH = c:\Harbour
CPATH = "c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC"
SDKPATH = "c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A"

HPATHL = $(HPATH)\LIB\vc32
CPATHL = $(CPATH)\LIB
SDKPATHL = $(SDKPATH)\LIB

HOPT = /n /gc0 /q $(Compiler Options) /i$(HPATH)\INCLUDE $(User Include Path&1) $(User Defines) $(Automatic Memvar Declaration) $(Variables Are Assumed) $(Generate Preprocessed Output) $(Warning Level)
COPT = -TP -W3 -c -I$(HPATH)\INCLUDE

LOPT = /nologo /subsystem:windows /force:multiple /NODEFAULTLIB:libc
LIBS1 = $(FWH)\LIB\FiveHm.lib $(FWH)\LIB\FiveHCm.lib
LIBS2 = $(HPATHL)\hbrtl.lib $(HPATHL)\hbvm.lib $(HPATHL)\gtgui.lib $(HPATHL)\hblang.lib $(HPATHL)\hbmacro.lib $(HPATHL)\hbrdd.lib $(HPATHL)\rddntx.lib $(HPATHL)\rddcdx.lib $(HPATHL)\rddfpt.lib $(HPATHL)\hbsix.lib $(HPATHL)\hbdebug.lib $(HPATHL)\hbcommon.lib $(HPATHL)\hbpp.lib $(HPATHL)\hbcpage.lib $(HPATHL)\hbwin.lib
LIBS3 = "$(SDKPATHL)"\kernel32.lib "$(SDKPATHL)"\user32.lib "$(SDKPATHL)"\gdi32.lib "$(SDKPATHL)"\winspool.lib "$(SDKPATHL)"\comctl32.lib "$(SDKPATHL)"\comdlg32.lib "$(SDKPATHL)"\advapi32.lib "$(SDKPATHL)"\advapi32.lib "$(SDKPATHL)"\shell32.lib "$(SDKPATHL)"\ole32.lib "$(SDKPATHL)"\oleaut32.lib "$(SDKPATHL)"\uuid.lib "$(SDKPATHL)"\odbc32.lib "$(SDKPATHL)"\odbccp32.lib "$(SDKPATHL)"\iphlpapi.lib "$(SDKPATHL)"\mpr.lib "$(SDKPATHL)"\version.lib "$(SDKPATHL)"\wsock32.lib "$(SDKPATHL)"\msimg32.lib "$(SDKPATHL)"\oledlg.lib
LIBS = $(LIBS1) $(LIBS2) $(LIBS3)

[Environment]
PATH = $(HPATH)\BIN;$(CPATH)\BIN;%PATH%
INCLUDE = $(HPATH)\INCLUDE;$(CPATH)\INCLUDE;$(FWH)\INCLUDE
LIB = $(HPATH)\LIB;$(CPATH)\LIB
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 = $(DCon)

[Show Makefile]
Title=Show makefile
Cmd0=uestudio makefile
ShowWindow=1
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 $(LIBS1) $(LIBS2) "$(SDKPATHL)"\kernel32.lib "$(SDKPATHL)"\user32.lib "$(SDKPATHL)"\gdi32.lib "$(SDKPATHL)"\winspool.lib "$(SDKPATHL)"\comctl32.lib "$(SDKPATHL)"\comdlg32.lib "$(SDKPATHL)"\advapi32.lib "$(SDKPATHL)"\advapi32.lib "$(SDKPATHL)"\shell32.lib "$(SDKPATHL)"\ole32.lib "$(SDKPATHL)"\oleaut32.lib "$(SDKPATHL)"\uuid.lib "$(SDKPATHL)"\odbc32.lib "$(SDKPATHL)"\odbccp32.lib "$(SDKPATHL)"\iphlpapi.lib "$(SDKPATHL)"\mpr.lib "$(SDKPATHL)"\version.lib "$(SDKPATHL)"\wsock32.lib "$(SDKPATHL)"\msimg32.lib "$(SDKPATHL)"\oledlg.lib

[.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) -o$O $I

[.RC]
Out = $In.res
Cmd0 = c:\vc98\bin\rc -r -fo$O $I

IncFiles = 1
CaseSensitive = 0
IncDirs = .;$(INCLUDE);
IncKeyWords = #include;
Comments = /*.*/.//.eol.
 

uestudio\projects\Harbour\window_vc32.wiz

Code: Select all  Expand view

##############################################################################
#                                                                            #
#             UEStudio's User Defined Project Template                       #
#                                                                            #
# The following template is to be modified by the user.  It describes        #
# individual preferences for new project creation.                           #
#                                                                            #
# The first and most important section is [UDT] which contains a "Compiler"  #
# variable and a list of seed files to be inserted in the newly created      #
# project.  The Compiler variable specifies the name of the compiler's       #
# configuration directory, and the compiler configuration file.              #
# For example:                                                               #
# Compiler = Microsoft Visual C++ Compiler\Win32 Console Application         #
#                                                                            #
# The list of project files may be any combination of source, header,        #
# resource, and data files.  An example follows:                             #
#  File0=MyApp.h                                                             #
#  File1=MyApp.c, Source Files                                               #
#  File2=MyApp.ico                                                           #
# and so forth....                                                           #
#                                                                            #
# All subsequent section(s) of this template describe the contents of one    #
# or more of the project files defined above.  An optional group name may    #
# be specified after the file name.  In the above example, the group         #
# "Source Files" will automatically be created and MyApp.c will be included  #
# in the group folder.                                                       #
#                                                                            #
# For binary file contents such as Resource, Icon, or any other data file,   #
# where it is inconvenient to describe the contents in a script, the         #
# following format may be used:                                              #
# [File2]                                                                    #
# INCLUDEBINARY=c:\my_data_files\ico_data.raw                                #
# This will create [File2], in this case "MyApp.ico", with the content       #
# ico_data.raw                                                               #
#                                                                            #
# Alternately, binary file contents may be defined in this template using    #
# the ":HEX" directive.  This specifies that all data is represented as      #
# hexadecimal values.  For example:                                          #
# [File3:HEX]                                                                #
# 0065 66 F0, 0FF0, 0F0F0F0F                                                 #
# 12, FF, 20; 0F 40                                                          #
#                                                                            #
# where all numbers above are interpreted based on data length, as follows:  #
#  1-2 = bytes, 3-4 = words, 5-8 = dwords, >8 = an array of bytes.           #
#                                                                            #
# Predefined variables may be used to specify the names of files as well as  #
# the content of the files, e.g.:                                            #
# USER (user name), COMPUTER (computer name), TIME, DATE, PRJPATH (project   #
# path), PRJNAME (project name), PRJDIR (project directory)                  #
# Example: File0=$(PRJNAME).cpp                                              #
#                                                                            #
##############################################################################

[UDT]

Compiler = Harbour\Application_vc32

File0 = $(PRJNAME).prg
File1 = $(PRJNAME).rc

[File0]
#include "FiveWin.ch"

function Main()

   local oWnd
   
   DEFINE WINDOW oWnd TITLE "Test"
   
   ACTIVATE WINDOW oWnd
   
return nil

[File1]
#include <winapi.ch>

[Andrés González]

Antonio, como no tengo mucho tiempo siempre ando a salto de mata. Instalé VC2010 Express y ahora buscando en el foro y he encontado esta configuración de UESTUDIO para VC32, pero veo un SDK que no se de donde sale puesto que el VC2010 Express no me lo ha instalado. Puedes poner el link de donde lo descargas.

Code: Select all  Expand view

SDKPATH = "c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A"

La verdad es que he encontrado varios links, pero lo que no se si va en función de la versión del VC32. He visto algunos del 2008. Bueno si tienes un minuto por favor mira si me dices como va el tema.

[Andrés González]

He encontrado el SDK 2010 en los adicionales de la versión comercial, me confirmas si se trata de esto: http://msdn.microsoft.com/es-es/vstudio/ff655021

[Andrés González]

Sorry Google Traslation to spanish was running.

[Antonio Linares]

Andrés,

You may use the SDK that VC Express has installed

[Andrés González]

Ok, Thanks.