In article <PfSdnYil8MWpW5zVRVnyjwA@[EMAIL PROTECTED]
> donl@[EMAIL PROTECTED]
writes:
>
> "Stephen Quinn" <stevejqNO@[EMAIL PROTECTED]
> wrote in message
> news:3rjMj.1188$ko5.98@[EMAIL PROTECTED]
> > Donald
> >
> >> How does Clipper S87 include the library during a compile? I need to
> >> change some code in a library and have never needed to do this
before?
> >> Guess I need an overview...
> >
> > If you modify a routine and include it before the library in your link
> > script then the new code should be used in your app.
> > Eg Blinker extract
> > FILE XYZ.OBJ
> > LIB LIB_CONTAINING_XYZ_OBJ.LIB
> >
> > --
> > CYA
> > Steve
> >
>
> Thanks Steve
> (are you chained to your PC ? :-))
It appears that way as seen from the uk :-) Obviously nobody
sleeps "down under"...
> The file I refer to is called LIB_GEN.PRG - how do I generate the OBJ
file
> from this?
>
> Dona.ld.
Hi Donald,
Is LIB_GEN the source of the entire library? If so, just ****
the changes you need and compile it to a .obj using something
like
clipper lib_gen -m
then relink your app moving 'lib_gen' from LIB to FILE, for
example if before you had
plink86 output app.exe FILE app,blah LIB lib_gen,clipper
use
plink86 output app.exe FILE app,blah,lib_gen LIB clipper
Does that make sense? (I used to use plink86 rather than blinker
but I believe the syntax is very similar.)
The alternative, if you want one and have LIB.EXE, is to use this
latter to create lib_gen.lib from the .obj file created above. I
forget the syntax for LIB.EXE but it's straightforward; doing it
this way means that you would not need to alter your link script.
Hope that helps!
Pete
--
"We have not inherited the earth from our ancestors,
we have borrowed it from our descendants."
|
