From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b810defb48ddb4e3 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-11-30 14:45:18 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!howland.reston.ans.net!gatech!udel!news.mathworks.com!newshost.marcam.com!charnel.ecst.csuchico.edu!olivea!news.hal.COM!halsoft.com!netcomsv!telesoft!east.alsys.com!news From: jlo@east.alsys.com (John Lo) Subject: Re: Alsys ActiveAda Compiler Message-ID: Sender: news@alsys.com Organization: Alsys, Inc. X-Newsreader: Date: Wed, 30 Nov 1994 20:15:50 GMT Date: 1994-11-30T20:15:50+00:00 List-Id: Chris Gentle writes: > >Is anyone out there using the new Alsys ActiveAda 32-bit compiler for Windows? >The project I'm working on just got a copy and we've already found problems. >We have Ada code interfacing to several C modules. However, the compiler will >not link the object files output by our various C compilers (Visual C++ 1.5, >Borland C++ 4.02). > >If anyone else is having this problem, let me know. I can send more details >about the problem then. Don't want to clutter up the message if no one else is >using the compiler. > >Thanks, > > >Chris >gentlec@ifte.sed.redstone.army.mil > > > > > The ActivAda release note does specify which specific C compiler you can interface to. If you are building a DOS program, you need to use the MetaWare High C/C++ V3.x for DOS. If you are building a Windows (Win32s) program, you need to use the Microsoft Visual C++ 32-bit edition. Interface to Borland C++ is not supported. Visual C++ 1.5 is a 16-bit compiler and therefore would not work either. John