Convert DOS application(s) to Harbour <== LIB compatibility

[Antonio Linares]

You need a compatible version with MinGW

[elrosa]

Is there a way to find out which compiler is compatible with this library? Is there a fingerprint left by the compiler used to create the prohp lib/obj?

[Enrico Maria Giordano]

Is there a way to find out which compiler is compatible with this library? Is there a fingerprint left by the compiler used to create the prohp lib/obj?

That lib is probably a 16 bit lib so it's not compatible at all with any 32 bit compiler.

EMG

[elrosa]

I am afraid it is also

So that means I have to strip al print functionalities...

Oslib and CTP lib are also not compatible, but do not know yet which functions are effected. Will find out after stripping print ...

The Lfn lib (http://www.ousob.com/ng/lfnlib/ng1a2d0.php) is linked, but it doesn't work. I suppose there will be a similar function(s) which could do the same within Harbour?

So probably the worst case I am looking at is rebuilding all the output forms. Any suggestions for quickly rebuilding output forms?

[elrosa]

Oke, dbfcdx.lib also not recognized?

[Enrico Maria Giordano]

What compiler are you using? If Harbour try rddcdx.lib.

EMG

[elrosa]

Grrrr... let me quess... Clipper FPT isn't compatible also with Harbour

I cannot open any DBF with FPT associated (that is probably the DBFCDX/1001 error I am getting, because any DBF without FPT is opened with no problem)

Is there a way to make these DBF/FPT Harbour compatible without losing any data in the FPT (memo)

Maarten

[Enrico Maria Giordano]

xHarbour: dbffpt.lib
Harbour: rddfpt.lib

EMG

[elrosa]

Nop, still getting the 'DBFCDX/1001 Open error' message...

I found the following on this board:

If you are working with DBF/CDX/FPT files created with Clipper, Comix or Six Driver, let me tell you that those FPT files are not compatible with xHarbour FPT structure, this is due because Clipper and friends create FPT files with a "memblock" size of 16 bytes which is not compatible with (x)Harbour FPT memoblock, which is 64 bytes long, so any operation performed over the memofile will fail.

Is this not the problem I am facing?

Here my HBP file.

Code: Select all

# ------------------------------------------------- --------------------------------
# Executable name
# ------------------------------------------------- --------------------------------
# -o output file name
-oems.exe

# ---------------------------------------------------------------------------------
# Libraries
# ---------------------------------------------------------------------------------
# l Policy to link with the library. must omit path, extension, and the prefix 'lib' (... unless part of the name of file).

-lrddfpt 
-rddcdx 
-lhbgt
-lgtwvg
-lgtwvt
-lhbct
-lhbwin
-lhbnf
-lxhb
-lhbblink

# ---------------------------------------------------------------------------------
# Paths additional Includes
# ---------------------------------------------------------------------------------
# -i |-incpath=   Additional patches for research headers files
#-incpath=

# ---------------------------------------------------------------------------------
# Way of Lib PROC And HGAC 
# ---------------------------------------------------------------------------------
# -L-additional path to search for libraries
#-Li:
#-Ld:\users\hproc\lib;

# ---------------------------------------------------------------------------------
# other Parameters
# ---------------------------------------------------------------------------------
# .\OBJ\ Writes the .s and .o files in OBJ subfolder
# ---------------------------------------------------------------------------------
# -workdir=Working directory Policy to the build working directory.
#                     (default: .xbmc/play/comp in incremental mode, OS temp directory otherwise).
-workdir=.\OBJ
-gtgui

# ---------------------------------------------------------------------------------
# -[no]head[=]     Control source header parsing (in incremental build mode)
#                      can be: native (uses compiler to extract
#                     dependencies), full (default, uses simple text parser on
#                     the whole file), dep, off.
#-head=full

# ---------------------------------------------------------------------------------
# /n[]          No implicit starting procedure
#                     : 0=no implicit starting procedure
#                             1=no starting procedure at all
#                             2=add starting procedure if necessary
#-n

# ---------------------------------------------------------------------------------
# -compr=def         Metodo de Compressao UPX
#-compr=max

# ---------------------------------------------------------------------------------
# -pause         Performs a break in the case of compiler warning
#-pause

# ---------------------------------------------------------------------------------
# -[no]warn[=lev]     Sets the warning level (warning) C compiler
# Can be: max, yes, low, in, def (default: yes).
#-nowarn

# ---------------------------------------------------------------------------------
# -inc                Enables or incremental mode incremental.
#-inc

# ---------------------------------------------------------------------------------
# -[no]debug          Add / Delete debug information from the C compiler
#                     To compile with Harbour use the -b option as usual
#-b

# ---------------------------------------------------------------------------------
# -d        Policy to build ifdef
#-dHARBOUR

# ---------------------------------------------------------------------------------
# -icon=        Arrow icon for the application. must have a
# Format compatible with the target platform.
# Policy to inform the application icon.
#-icon=harb_win.ico

# ---------------------------------------------------------------------------------
# /u[]          Use set command (or no) Policy to load header file (.c) for all
# application.
#-u

#-w3 -es2
-gui

#-mt
# ---------------------------------------------------------------------------------
# Prg(s) and Rc(s) of the system
# ---------------------------------------------------------------------------------
overige.prg    
rk.prg
ag.prg
rd.prg
hs.prg
conver.prg
fax.prg
print.prg
browse.prg
getsys.prg
errorsy.prg
rddsys.prg
oops.prg
tn.prg
tn1.prg
tn2.prg
pr.prg
pr2.prg
pr_toep.prg
toep_br.prg
callrap.prg
rl.prg
rl2.prg
rl3.prg
or0.prg
or1.prg
or2.prg
or3.prg
or4.prg
or5.prg
nc_ver.prg
nc_aan.prg
ems.prg
ems2.prg
prspec.prg
euro.prg
budget.prg
html.prg
#party.prg
menuto.prg
div1.prg
div2.prg
div3.prg
hmenu.prg
kostpr.prg
snelcalc.prg
prbudget.prg
brutow.prg
monsters.prg
alloc.prg
pr_overz.prg
pdf.prg
vis.prg
combi.prg
combi2.prg
log_dien.prg
dien_log.prg
levtar.prg
zeevrach.prg
st.prg
reach.prg
 

[Enrico Maria Giordano]

Can you send me the DBF and the FTP to test them here?

EMG

[elrosa]

Done, send by wetranser to email: e.m.giordano@emagsoftware.it

[Enrico Maria Giordano]

Your database opens fine here. Let's make one step at a time. Are you using Harbour or xHarbour?

EMG

[elrosa]

Harbour from https://sourceforge.net/projects/harbour-project/

Code: Select all

hbmk2 ems.hbp > comp.log 2> warnings.log

[Enrico Maria Giordano]

Ok, so you have to link at least these libs:

Code: Select all

hbrtl +
hbvm +
hbcommon +
hbmacro +
gtwin +
hbrdd +
hbsix +
rddntx +
rddfpt +
rddcdx +
xhb +
hbwin +
 

EMG

[elrosa]

Ok, linked the following files:

• -lhbrtl
  -lhbvm
  -lhbcommon
  -lhbmacro
  -lgtwin
  -lhbrdd
  -lhbsix
  -lrddntx
  -lrddfpt
  -lrddcdx
  -lxhb
  -lhbwin
  -lhbct
  -lhbnf

No compile errors, but still got the same error.

Code: Select all

  Error DBFCDX/1001  Open error: .\X_CT
  Called from DBUSEAREA(0)
  Called from NETUSE(659)
  Called from USESAFE(434)
  Called from INTRO(2189)
  Called from MAIN(757)