Privacy and Security Notice
Archived Messages for CLAS_OFFLINE@cebaf.gov: A few questions about the build scheme
A few questions about the build scheme
Joseph Manak (manak@jlab.org)
Sat, 11 Apr 1998 16:04:16 -0400
I guess it is known that when you type make lib
in bankdefs it creates two include files in the
include area - you then get into quite a mess when
you check out a version of the code including the
include area and then try to
make all the libraries and your makefile decides to overwrite
your include area and places a possibly inconsistant
include file in there! - This sort of defeats the point
of checking out
a version of the include area to begin with... What's the
point of this aside from messing with my mind...? I mean
we could make every makefile ovewrite a source file in every other
area and then nobody would know what they are really checking
out...it would be cool...but nothing would get done...
I digress...
By the way the include file clas_offsets.inc was last committed to
the repository on 11/20/97!!! It is most surely out of date -
I know some code is using it now the tracking area so when you build with
the master makefile and it walks through /bankdefs before
/trk, disaster strikes and you cant build trk anymore! However
if you just check out the release and build trk by hand you
don't have any trouble. We should disable this insidious feature
posthaste - no makefile should be allowed to run amok and write over
source code in other packages!
Second, what is rec_work.o? How do I make it and why does
recsis need it? and why can't I make it anymore?
- Joe