Interfacing Alsys with Borland C++

Interfacing Alsys with Borland C++

[John E. Gleason]

I have a little problem. I am using Alsys 5.1.1 and I am trying to
create a graphical interface for an application I have written. The
problem is that the graphics routines are in C compiled with Borland's
C++ compiler. Well I HAVE READ the manuals and the procedure the manual
describes does not work.
                1. I declare the external procedure
                2. I use pragma INTERFACE ( <language>, <ada proc-name>)
                3. I use pragma INTERFACE_NAME ( <ada-proc-name>,
                                                 <lang-proc-name>)
 The probelm is not the compiling, but the binding !!! I get an Alsys
.OBJ file and a Borland-C .OBJ file. I call the binder after setting my
library, module=C.OBJ, and the search=INTERF.LIB. Well the INTERF>LIB
(the Alsys C-interface library) is not compatible with Borland C++ and I
get the foolowing map file from the linker....

-------------------------------------------------------------------------
Alsys 386 DOS Ada Binder, Version 5.1    (created at 15:42:57, May 27, 1992)
Bind of MAIN from C:\BLUE\ADALIB at 17:33:12, May 16, 1993.

==============================================================================
Start of linker messages.
386|LINK: 4.0 -- Copyright (C) 1986-91 Phar Lap Software, Inc.
Error: Undefined symbol "_MWFINIT" in module "initc" at location 00005764.
Error: Undefined symbol "_MWCFINIT" in module "initc" at location 00005769.
Error: Undefined symbol "_MWCFTERM" in module "initc" at location 0000577E.
Error: Undefined symbol "_MWHALT" in module "initc".
Error: Undefined symbol "_MWSET_UP_ARGS" in module "initc".
Error: Undefined symbol "SMALL?" in module "initc".


End of linker messages.

Bind: ** Linker return code indicates errors.

-----------------------------------------------------------------------------

So, either I am doing something wrong or Alsys is not compatible with
Borland C++. Whatever the reason, I know there is a way to do it and
someone out there knows the answer.Pleas help!!!


P.S. I've tried not including INTERF.LIB..., including extra
     C-LIB's,....building an assembler-code bridge to call the C program
     NOTHING WORKS.

P.S.S. My co-programmer MBOYER posted mail about this but wasn't
specific in defing the problem. I appreciate the responses from the
people who weren't smart-asses and didn't just say read the manual or
retype the manual's example.... thank you.

respond to jgleason@bird.cs.ohiou.edu
           John E. Gleason III

 Thanks