Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How do I compile 5.01 code using Clipper 5.3? 1

Status
Not open for further replies.

Rahja

Programmer
Mar 4, 2007
16
CA
I have an Inventory program that I wrote with Clipper 5.01 and would like to start making some enhancements to it with 5.3 functions. The problem I'm having is getting it to use Blinker. The original was done with RTLink. Does anyone have some suggestions, or directions?

Thanking You in Advance!
 
The new complier should be fine with your old code. I'm guessing you got everything to compile since you say the problem is with the linker.

Here is an example of a link file I use that takes advantage of some Blinker 5 features.

Code:
blinker message duplicates
blinker incremental off
blinker executable clipper f51
OUTPUT l_menu
BEGINAREA
   SECTION INTO l_menu
   file l_menu
   file l_procs
   file cmb_proc
   file l_dlog
   file horse
   file help
   FILE L_LICENS
   file L_WINDOW
   file L_CHGOWN
   file L_COLORS
   file L_REINDX
   file L_LTYPES
   file l_tax
   file L_TRACK
   file L_LEASE
   file L_LICENL
   file L_LEASEL
   file L_TYPEFL
   file L_TRACKL
   file L_STATSL
   file L_LXTYPL
   file L_FILELL
   file L_LPACK
   file L_MULTI  
   file L_MULTIL
   file L_LOCATE
   file L_SPOUSL
   file L_LNEWCL
   file L_RULING
   file L_RULINL
   file l_changy
   search oke.lib
ENDAREA
@cl520opt

What, specifically, are you having a problem with when trying to use Blinker?


Lyndon

---People Remember about 10% of what you say ---They never forget how you made them feel. Covey
 
Thanks Lyndon for your immediate response. Yes, I do have all the prg files for the program. I guess the problem I am having is trying to determine what syntax I need for the Linker, and also what Linker to use. From what I can determine there is both the Blinker and the Exospace available to use. The following is the syntax I use to compile and link under 5.01 using RTLink.

Clipper @Flaman1.clp
Clipper @Flaman2.clp
RTLINK Dynamic into Flaman FI Flaman1.obj,Flaman2.obj OU Flaman.exe LIB CLD, Extend

My goal is to ensure the compiling and linking is working fine with my current prg files, and then I can start writing code to encompass some of the 5.3 functionality. Any help or advice I can receive will be most greatly appreciated.

Brian

 
What version of blinker do you have? Then I'll send you an example link script.

Lyndon

---People Remember about 10% of what you say ---They never forget how you made them feel. Covey
 
Thanks Lyndon, it is Blinker Version 1.00

 
Blinker 1.0 won't support all of 5.3's functions. You will need at least 3.0 but Blinker 5.x is best.

I've never used Exospace. You should check the docs and see if your version works with Clipper 5.3.

Check these sites and for lots of good Clipper info.


Following will link your current code with Blinker 1.0. Just put this code in a link file and execute it as follows:

blinker @linkfile.lnk
Code:
blinker executable clipper f51
OUTPUT flaman
BEGINAREA
   SECTION INTO flaman
   file Flaman1.obj
   file Flaman2.obj 
ENDAREA
LIB CLD
LIB Extend

Lyndon

---People Remember about 10% of what you say ---They never forget how you made them feel. Covey
 
Blinker 1.0 and Exospace were bundled with Clipper 5.3. Blinker supports overlaying, EXOSPACE using of extended memory.
Here is my batchfile I used to compile, link and execute any simple clipper program:
------
@ECHO OFF
call c:\dos\clp\bin\_SetEnv.bat
clipper %1 /m /n > %1.err
if errorlevel 1 goto ERR
%LINKER% file %1 LIB jb_std,jb_stdl >> %1.err
if errorlevel 1 goto ERR
%1.exe
goto KONEC
:ERR
readme %1.err
:KONEC
-------

%LINKER% must be set in _SetEnv.bat, where I used both of them - BLINKER or EXOSPACE.
%1 is a param of this batchfile - name of compiled program without extension.

batchfile _SetEnv.bat:

set PATH=c:\dos\bin;c:\dos\clp\bin;%PATH%
set INCLUDE=c:\dos\clp\include
set LIB=c:\dos\clp\lib
REM set LINKER=EXOSPACE
set LINKER=BLINKER


 
I've found Blinker 1.0 to lock so often I went to 3.0 and no longer had those problems.

Lyndon

---People Remember about 10% of what you say ---They never forget how you made them feel. Covey
 
Thanks Lyndon, that worked perfect. Now I can start builing in some new features.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top