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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8322da3f8f90f31d X-Google-Attributes: gid103376,public From: labtek@cs.yale.edu (Tom Griest) Subject: Re: gnat3.04a1 on Win95: linking a DLL Date: 1996/08/25 Message-ID: <4vqsgtINNaiu@RA.DEPT.CS.YALE.EDU>#1/1 X-Deja-AN: 176454978 distribution: World references: organization: Yale University Computer Science Dept., New Haven, CT 06520-2158 newsgroups: comp.lang.ada Date: 1996-08-25T00:00:00+00:00 List-Id: westley@buffnet.net (Terry J. Westley) writes: >Newbie on Windows 95 searching for info on how to "link" a GNAT Ada program >with a DLL. Actually, I want to know how to tell the linker NOT to attempt >to resolve a reference to a symbol I know to be in the DLL. The linker must resolve dynamically linked objects to a dll entry point. Linking with a DLL is done in an almost transparent way. You simply link with the existing .lib file. Now if what you mean is making a binding to an existing library, then you can use pragma Import. Use C as the calling convention unless the calling convention is STDCALL in which case use stdcall. Also, note that for DLL data you should use stdcall to insure indirect references are generated. -Tom LabTek Corp.