Modifying zApp 3.0 Makefiles to use Borland v5.02 compiler

Article ID: 1021
Last updated: 05 Feb, 2008
Article ID: 1021
Last updated: 05 Feb, 2008
Revision: 1
Views: 2554
Posted: 19 Jan, 1998
by Dean J.
Updated: 05 Feb, 2008
by Dean J.
Problem


zApp 3.0 makefiles work correctly with Borland v5.0x, but do not compile or link correctly when used with Borland v5.02.


Cause


Borland modified the syntax accepted by TLINK32 between v5.0x and v5.02.


Action


The syntax difference for Borland v5.02 is that you can no longer use + (plus) signs to separate object files and libraries on a link line. A + is, however, required on the end of a line if more files of the same type appear on the next line.

Change the makefile as follows.

Old version:

!if $(COMPILER)==bc5
bc5dll: $(OFILES)
tlink32 /aa $(DLLFLAGS) @&&~
c0d32.obj+$(OFILES)
..libznp03b9$(DB).DLL
zpn03b9$(DB)

import32.lib+ctl3d32.lib+cw32i.lib+ole2w32.lib+$(ROGUE)libtld.lib zpn03b9$(DB)

New version should look like this:

!if $(COMPILER)==bc5
bc5dll: $(OFILES)
tlink32 /aa $(DLLFLAGS) @&&~
c0d32.obj
$(OFILES),..libznp03b5$(DB).DLL,zpn03b5$(DB),import32.lib ctl3d32.lib
cw32i.lib ole2w32.lib $(ROGUE)libtld.lib,zpn03b5$(DB)

You may also need to add the -tWM- compiler option to ensure that your app is single threaded. 

The compiler option is set with the following line:

CPPFLAGS=$(PFLAGS) $(DEBUGLIB) $(DEBOPT) -V -3 -d -x -tWM- -H=zapp.sym
-D__NT__=1 $(C3D)
This article was:   Helpful | Not helpful
Report an issue
Article ID: 1021
Last updated: 05 Feb, 2008
Revision: 1
Views: 2554
Posted: 19 Jan, 1998 by Dean J.
Updated: 05 Feb, 2008 by Dean J.

Others in this category