🚀 go-pugleaf

In article: <4a3h8r$j38@azure.acsu.buffalo.edu>  rastrl@cs.buffalo.edu 
(Robert L Rast) writes:

> 	I've been down this road before with TS 1.17. 
> 	What compiler is XLib from?

I'm not blindingly sure, the doumentation is rather sketchy, and although 
the source files are obviously C, I am still in considerable doubt as to 
exactly which compiler.
 
> 	Are you prepending an underscore on your object names in 
> 	the definition modules.  Chances are, the objects in the XLib
> 	has them. Also, put a: (*$G-*) in the .def files. This is a 
> 	directive to the compiler to not prefix object names with the
> 	module name.

I had tried putting underscores before the variable names, but with little 
success, however i had *not* put the (*$G-*) compiler directive in, so I 
will try that as well.

> 	I had problems using the (*$K+*) directive (use C calling 
>	convention).

Wow! Well, I do have plenty of time on my hands right now, so I will take 
care to work around these obstacles.... thanks a lot, because some of these 
problems are not at all clear from first sight.
 
> 	You might have to extract everything (.obj) out of the library. 
> 	I don't think TS 1.17 supports libraries.  If you do this, you 
> 	will probably have to write .def for each .obj even if a .obj
> 	object is not referenced in your .mod files. 
> 	Then just do:
> 
> 		IMPORT somename;   (* for linker resolution *)
>  

I had a sinking feeling that I might have to write def files for every 
module. I'll experiment, and see what happens.


> 	Let me know how it goes,

I certainly will.


Martin Harvey  (mch24@cam.ac.uk)