UESTUDIO

[Andrés González]

Have someone the config files for fivewin and mingw or visual studio in UESTUDIO? I need that to do some test in my holidays, during my work is hard to do. Please any help.

[Antonio Linares]

Andrés,

Tim Stone is successfully using UEStudio with MSVC 2010, so he has the config files, etc.

Not sure if he already posted them here in the forums.

[TimStone]

Sorry for the delay ... Antonio brought this to my attention early this morning, but its been a very busy day so far.

Here is my implementation for MSVC. It is for the compiler Configuration file. Use Harbour under configs, and modify it with the proper paths for your system. I did remove my extra libraries that you would not need. I keep those in the C:\Harbour\UserLibs folder. Using the UE built in compiler configuration editor make your changes to match this model. In UE Studio, you do this under Build - Select Compiler.

If Harbour is not listed on your UE Studio list, you can go to your \FWH folder, look under \uestudio, and you should see a zip fwh file. In that is a configs folder, with a Harbour folder. Copy the Harbour folder to your C:\Program Files (x86)\IDM Computer Solutions\UEStudio\configs folder. Then you can select it in UE and modify the content.

Tim

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 = C:\Project\ABC.exe
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:\fwh
HPATH = C:\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
CPATHL = $(CPATH)\LIB
SDKPATHL = $(SDKPATH)\Lib
UPATHL = C:\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 ace32.lib rddads.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 =

LIBS = $(LIBS1) $(LIBS2) $(LIBS3) $(LIBS4) $(LIBS5) $(LIBS6)


[Environment]
PATH = $(HPATH)\BIN;$(CPATH)\BIN;$(SDKPATH)\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 mls9.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 = rc -r -fo$O $I

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

 

Make sure your paths are all correct.

[Andrés González]

Thanks Tim, I was making changes to the Visual studio config files and no way, very complicated. Yours are easy to set up, thanks for your explanation.

[Antonio Linares]

Tim,

Thanks!

[TimStone]

Andres,

Antonio has been very patient, and helped me get this whole system working. I am completely satisfied with the result.

I use the latest Harbour ( 3.0 ) build posted on the FWH site
I use FWH 12.06
I'm using Microsoft Visual Studio 2010. I do have the beta for 2012 but have not tried that at all
I use the most current version of UE Studio. It makes it very easy because when I have a project, and add a file to that project, it is automatically added to the build. ONE NOTE: I would suggest if you add a new file(s) to a project, either select the option to create a new makefile, or Rebuild all.

Finally, one other note. In UE you can have a debug or release build. I encountered some issues with the debug assembly, so I just build in Release mode.

The success of being able to use FWH with Harbour and Visual Studio is a real community effort. With my "advancing age" I often forget things I've known for years, but someone here is always willing to help. If you have problems, just ask, and people will respond.

Tim

[Antonio Linares]

Dear Tim,

The real good thing about this users forums is that we are friends helping each other

thanks!

[Andrés González]

Thanks Tim, I was busy during the weekend but just tested in home and working ok. Just a question about which debugger do you use, the one that comes with fivewin (Carles debuger) or windbg from microsoft. I found a book that explain how to use windbg with VS2010 and I want to try it, just to learn. Any advise?

Thanks

[TimStone]

Right now I'm not linking in a debugger. I'm only using the errorsys program.

I would say give it a try and see which one works for you, then share it here.

Tim

[Antonio Linares]

Andrés,

It may be very interesting to be able to use windbg. From it we can not debug PRG code, but it can be very usefull for low level C code

Is it a book that explains it ?

[Andrés González]

Inside Windows Debugging: A Practical Guide to Debugging and Tracing Strategies in Windows By Tarik Soulami
2012 | 592 Pages | ISBN: 0735662789

[Antonio Linares]

Andrés,

Muy interesante, gracias por la info!

[Andrés González]

Please Tim, the other day I tested VS with a single file and was ok, but today when I mount my project with over 30 files, just check 2 files with no errors and do nothing wich the others and never generate the exe. Do you know what could happend? With Borland work ok.

[TimStone]

Sorry for the delay. I was on vacation.

I installed UE Studio on a new notebook and its not building. I have to check it out further. I did make a switch on something but didn't make a note of it. I'll post the resolve when I find it.

I do know you may need to step up the error count in the Project Setup ( manager ? ). This will help you find which file is creating the problem. RIght now I think the default is 3. I put it to 200. There may be some issues that differ between Borland and Microsoft.

Tim

[Andrés González]

Please Tim, when you can do it, tell me where to set up this parameter.