UltraEdit

[Antonio Linares]

Carlos,

Esta es la configuración a usar en
c:\Archivos de programa\IDM Computer Solutions\UEStudio\configs\Harbour\FWH window:

Code: Select all | Expand

# --------- CLIPPER Compiler 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 = COMPILER OPTIONS
Warnings = no|yes
Assumed Variables = no|yes
Compiler Options = 
Libraries = 

[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.
Linker Options = Provides a space for you to specify an additional linker options.
Debugger=Provides a space for you to set the debugger you want to use to debug application.

[SettingsReps]
Warnings = yes=/w|no=
Assumed Variables = no=|yes=/v

[Variables]
BPATH = C:\BCC55
CPATH = C:\HARBOUR
COPT = /m /n /o$In $(Warnings) $(Compiler Options)
LOPT = $(Linker Options)
FWH = C:\FWH
LINKER = $(BPATH)\BIN\ILINK32

[Environment]
PATH = $(CPATH)\BIN;%PATH%;$(BPATH)\BIN
INCLUDE = $(CPATH)\INCLUDE;$(FWH)\INCLUDE
LIB = $(CPATH)\LIB
OBJ = $(CPATH)\OBJ

[General]
TargetExt = .EXE
ReleaseOut = Release
DebugOut = Debug
UseFullPaths = 0
UseDosNames = 1
Excludes = $(Excluded Files)

[MakeCommands]
run = Execute Application
debug = Start Debugger
makef = Show Makefile

[Execute Application]
Title = Execute $T
Cmd0 = $(Command Line Arguments)
Depends = $T
ShowWindow = 1
DisplayConsole = 0

[Start Debugger]
Title=Debug $T
Cmd0=$(Debugger) $T
Depends=$T
ShowWindow=1

[Show Makefile]
Title=Show makefile
Cmd0=uestudio makefile
ShowWindow=1
DisplayConsole=0

[InsertFiles]
group0 = $(Libraries)

[FileGroups]
FGO = .obj;
FGR = .res;
FGL = .lib;

[GroupFormats]
FGO = %s
FGR = %s
FGL = %s

[Build]
Out = $T
Depends = $FGO $FGR
Cmd0 = echo $(FWH)\lib\FiveH.lib $(FWH)\lib\FiveHC.lib + > b32.bc
Cmd1 = echo $(CPATH)\lib\b32\rtl.lib + >> b32.bc
Cmd2 = echo $(CPATH)\lib\b32\vm.lib + >> b32.bc
Cmd3 = echo $(CPATH)\lib\b32\gtwin.lib + >> b32.bc
Cmd4 = echo $(CPATH)\lib\b32\lang.lib + >> b32.bc
Cmd5 = echo $(CPATH)\lib\b32\macro.lib + >> b32.bc
Cmd6 = echo $(CPATH)\lib\b32\rdd.lib + >> b32.bc
Cmd7 = echo $(CPATH)\lib\b32\dbfntx.lib + >> b32.bc
Cmd8 = echo $(CPATH)\lib\b32\dbfcdx.lib + >> b32.bc
Cmd9 = echo $(CPATH)\lib\b32\dbffpt.lib + >> b32.bc
Cmd10 = echo $(CPATH)\lib\b32\hbsix.lib + >> b32.bc
Cmd11 = echo $(CPATH)\lib\b32\debug.lib + >> b32.bc
Cmd12 = echo $(CPATH)\lib\b32\common.lib + >> b32.bc
Cmd13 = echo $(CPATH)\lib\b32\pp.lib + >> b32.bc
Cmd14 = echo $(CPATH)\lib\b32\codepage.lib + >> b32.bc
Cmd15 = echo $(BPATH)\lib\cw32.lib + >> b32.bc
Cmd16 = echo $(BPATH)\lib\import32.lib + >> b32.bc
Cmd17 = echo $(BPATH)\lib\psdk\odbc32.lib + >> b32.bc
Cmd18 = echo $(BPATH)\lib\psdk\nddeapi.lib + >> b32.bc
Cmd19 = echo $(BPATH)\lib\psdk\iphlpapi.lib + >> b32.bc
Cmd20 = echo $(BPATH)\lib\psdk\rasapi32.lib, >> b32.bc
Cmd21 = echo ..\$Tn.res >> b32.bc
Cmd22 = $(LINKER) -Gn -aa -Tpe -s -v c0w32.obj $FGO, $Tn.EXE,, @b32.bc

[.PRG]
Out = $In.c
DebugFlag = /b
ReleaseFlag = /l
Cmd0 = harbour $(COPT) $R $I

[.C]
Out = $In.obj
Cmd0 = bcc32 -c -IC:\HARBOUR\INCLUDE $In.c

[.RC]
Out = $In.res
Cmd0 = brc32 -r ..\$In.rc

[ZeCarlos]

Boa Tarde

A configuracao que tinha estava quase igual.
Substitui pela que enviou e alterei as PATHS. Deu erro nos includes .h

Alterei a instrucao:

[.C]
Out = $In.obj
Cmd0 = bcc32 -c -IX:\xHARBOUR\INCLUDE $In.c

para:
[.C]
Out = $In.obj
Cmd0 = bcc32 -c -Ix:\xHARBOUR\INCLUDE -Ix:\BCC55\INCLUDE $In.c

-----
Deixou de dar erro.
Agora da:

Fatal: Unable to open file 'HBSIX.LIB'
email.exe - 0 errors(s), 0 warning(s)

E continua sem gerar o email.exe.

Nao encontro a HBSIX.LIB. Compilando com o buildx.bat dá o erro mas gera o executavel.
Se retirar a linha:
Cmd10 = echo $(CPATH)\lib\b32\hbsix.lib + >> b32.bc
não dá erro mas fico na mesma sem o email.exe

O ficheiro makefile que o UEStudio cria em:
X:\xHarbour\FWH260\SAMPLES\Release
continua a ter a linha que me da ideia que apaga o executavel depois de ser gerado:
CLEAN:
-@erase "email.res"
-@erase "email.c"
-@erase "email.obj"
-@erase "email.EXE"

------------------------------------

Utilizo o FWH 2.6 e o xHarbour 0.99.3 (simplex) que veio com o FWH 2.6

X:\BCC55\Bin\ilink32.cfg
/Lx:\bcc55\lib;x:\xHarbour\lib;x:\xHarbour\fwh260\lib

X:\BCC55\Bin\bcc32.cfg
-Ix:\bcc55\include;x:\xHarbour\include;x:\xHarbour\fwh260\include
-Lx:\bcc55\lib;x:\xHarbour\lib;x:\xHarbour\fwh260\lib

A versão do UEStudio é 05.10+1

Utilizando o buildx.bat do FWH ou o xMAte sem o hbsix.lib o executavel é feito sem problemas.


Obrigado
Jose Carlos

[Antonio Linares]

Jose Carlos,

Has comprobado que hbsix.lib existe y está en x:\xharbour\lib\b32 ?

[ZeCarlos]

Boa Tarde

Não tenho esse directorio. Tenho da instalação a partir das fontes do FWH 2.6:


x:\xHarbour
\bin
\doc
\FWH260 (Copia da instalação para este directorio)
\AVIS
\BITMAPS
\DLL
\ICONS
\INCLUDE
\LIB
\manual
\SAMPLES
\SOURCE
\tools
\include
\lib
\tests

x:\BCC55
\Bin
\Examples
\Help
\Include
\Gl
\Rw
\Sys
\Lib
\PSDK



-----------------------

Obrigado
Jose Carlos

[/img]

[ZeCarlos]

Bom dia

Assim é mais facil de ver


x:\xHarbour
x:\xHarbour\bin
x:\xHarbour\doc
x:\xHarbour\FWH260 (Copia da instalação para este directorio)
x:\xHarbour\FWH260\AVIS
x:\xHarbour\FWH260\BITMAPS
x:\xHarbour\FWH260\DLL
x:\xHarbour\FWH260\ICONS
x:\xHarbour\FWH260\INCLUDE
x:\xHarbour\FWH260\LIB
x:\xHarbour\FWH260\manual
x:\xHarbour\FWH260\SAMPLES
x:\xHarbour\FWH260\SOURCE
x:\xHarbour\FWH260\tools
x:\xHarbour\include
x:\xHarbour\lib
x:\xHarbour\tests

x:\BCC55
x:\BCC55\Bin
x:\BCC55\Examples
x:\BCC55\Help
x:\BCC55\Include
x:\BCC55\Include\Gl
x:\BCC55\Include\Rw
x:\BCC55\Include\Sys
x:\BCC55\Lib
x:\BCC55\Lib\PSDK

Obrigado
Jose Carlos

[Antonio Linares]

Jose Carlos,

Deberías tenerlo x:\xharbour\lib\hbsix.lib

[ZeCarlos]

Boa Tarde

Com a versão que me enviou FWH 2.6 vem o xharbour 0.99.3 e não existe essa LIB.
Fiz download do file www.fivetechsoft.com/files/xharbour.exe e este ja tem essa LIB mas é a versão 0.99.60.
Posso utilizar esta ultima versão com a versão do FHW que tenho ? Preciso de fazer alguma alteração ?


Obrigado

[Antonio Linares]

Jose Carlos,

Prueba con el xharbour que tenias anteriormente y usa:

... x:\xharbour\lib\dbfdbt.lib

en vez de:

... x:\xharbour\lib\hbsix.lib

[ZeCarlos]

Boa Tarde

Substitui o x:\xharbour\lib\hbsix.lib por x:\xharbour\lib\dbfdbt.lib conforme disse.
Não tem erros:
-------------------------
Borland Resource Compiler Version 5.40
Copyright (c) 1990, 1999 Inprise Corporation, All rights reserved.
email.EXE - 0 erro(s), 0 warning(s)
-------------------------
Mas não cria o email.exe. Os novos ficheiros que cria são:

no X:\xHarbour\FWH260\SAMPLES
........................ email.RES
........................ email.prj
........................ email.udp
no X:\xHarbour\FWH260\SAMPLES\Release
........................ b32.bc
........................ makefile
........................ email.obj
........................ email.c

e não cria mais nenhum ficheiro.
Será algum parametro do UEStudio ?

Obrigado,
Jose Carlos

[Antonio Linares]

Jose Carlos,

Busca por todo el ordenador el fichero email.exe

[ZeCarlos]

Ja procurei e nao encontra nenhum



Jose Carlos

[ZeCarlos]

Boa Tarde

Ja esta OK.

Em vez de apagar a instrução e renumerar os CMD deixei a linha assim:
------
Cmd10 = echo $(CPATH)\lib\b32\dbfdbt.lib + >> b32.bc
#Cmd11 = echo $(CPATH)\lib\b32\hbsix.lib + >> b32.bc
Cmd12 = echo $(CPATH)\lib\b32\debug.lib + >> b32.bc

-----

Depois de retirar a linha e renumerar os CMD
----
Cmd9 = echo $(CPATH)\lib\b32\dbffpt.lib + >> b32.bc
Cmd10 = echo $(CPATH)\lib\b32\dbfdbt.lib + >> b32.bc
Cmd11 = echo $(CPATH)\lib\b32\debug.lib + >> b32.bc
------------

deu erro:
---------
Fatal: Unable to open file 'CODEPAGE.LIB'
--------

Retirei a linha e renumerei
----
Cmd13 = echo $(CPATH)\lib\b32\pp.lib + >> b32.bc
Cmd14 = echo $(BPATH)\lib\cw32.lib + >> b32.bc
-----

e ficou a criar o email.EXE na pasta Release.


Nao é possivel alterar a pasta onde é criado o EXE ?

Tentei colocar
----
[Settings]
Target = x:\MyApp\Testes
Category&01 = DEFAULT RUN CONFIGURATION
Working Directory =.
Command Line Arguments =
Category&02 = COMPILER OPTIONS
Warnings = no|yes
Assumed Variables = no|yes
Compiler Options =
Libraries =
-----
mas continua a criar o EXE na pasta Release

Obrigado
Jose Carlos

[Antonio Linares]

Jose Carlos,

Me alegro que lo hayas solucionado.

No nos hemos planteado situar el EXE en otro directorio. Si consigues hacerlo, coméntanoslo. Gracias