Ned,
I'm not sure anybody is compiling inboard modules due to the size of
the resultant replacement executive. Are you sure that your new
executive is being used and not the old one? Why use inboards instead
of loadable modules?
I'll look into the reason that the dxfHWload function is not included.
David
I am running the latest CVS updates (libtool branch)
under Red Hat version 8.0. Many thanks to David
Thompson for the clues to make that happen. I am now
running into a problem with my user-defined inboard
modules. I notice that the top level README caries a
note about user defined modules being a known problem.
But the date on the file is July 1999; is this
relevant?
I'm now getting a clean load (except for a message
about sys_errlist). Initially there was an unsatisfied
external reference called dxfHWload. I suspect that
dxfHWload should be coming from libDX.a. I satisfied
the reference by forcing the link from the source
directory
/dx/src/exec/hwrender/opengl/.libs/libOPENGL.a.
The user interface is displaying the added module names
and configuration dialog boxes (so mdf2c is working).
But as soon as I try to use one of the modules I get
"<module name>: function does not exist. Operation not
implemented". I've been using some of these modules for
well over five years so I doubt that there are code
problems with _all_ the modules (besides, I'm not even
starting to execute the code in my routines). Has a
step been added since 4.2.0 to the procedure for
linking in modules that I missed? Perhaps the MDF file
is missing a new field?
Thanks for your time,
Ned Piburn
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
