Nope, linking to both isn't a problem, it's just a problem setting up
where to put object.o. If it's in libDXL, then we do have problems so
if we say it belongs with libDXlite, then I can look to see if there
are any problems there. I just want to make sure its okay to leave it
out of libDXL.
David
It looks like that code handles passing OpenDX objects back from OpenDX to
the application. You need a lot of stuff to un-serialize the objects.
For example, the user can install a handler to be called whenever an error
message is produced by OpenDX, or when OpenDX executes DXLOutput.
I think that if you want to use that functionality, you would link with
both libDXL.a and libDXlite.a. I don't think that the functionality has
to be incorporated into DXL. Is that a problem for libtool?
Greg
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)257-8530
