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.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: The best possible way to call a function in a shared library
Date: Wed, 11 Oct 2017 17:25:22 -0500
Organization: JSA Research & Innovation
Message-ID: <orm5oj$46t$1@franka.jacob-sparre.dk>
References: <9885a3fd-8ffa-4076-ba1f-db2f8035e0dc@googlegroups.com>
   <oqvdce$nqd$1@gioia.aioe.org>
 <5984e47c-cfe5-4d22-9907-f113f24647b9@googlegroups.com>
 <or046l$1d2$1@gioia.aioe.org>
 <2bc424a1-3559-42bb-9f40-22763c21e7f2@googlegroups.com>
 <lyk20b6jlp.fsf@pushface.org>
 <fcfede51-6871-4157-80b6-a88fdbeac475@googlegroups.com>
 <761a5a41-04de-4f48-aac2-f5fe167dabd5@googlegroups.com>
 <f25de074-0306-4293-b57d-a758f19ad2db@googlegroups.com>
 <or78t0$4ve$1@gioia.aioe.org>
 <41f9bb00-4fa3-472e-98e4-d32e5ae4e2d6@googlegroups.com>
 <or80ad$1kjq$1@gioia.aioe.org>
 <fbf50fa1-29be-48f4-a135-31cb9ff5db9a@googlegroups.com>
 <ora32c$ud0$1@gioia.aioe.org>
 <2f235de2-5969-4cf8-ada6-c0d886f0f9ac@googlegroups.com>
 <orak91$1oak$1@gioia.aioe.org>
 <a0f548f7-eaa3-48bb-b35b-bdfefadb439e@googlegroups.com>
 <orih4t$jg$1@gioia.aioe.org>
 <2d6225df-f847-4324-a7f0-e4544d0b5b44@googlegroups.com>
 <orkg0u$13o4$1@gioia.aioe.org>
 <18781206-12b4-4da8-ac8c-96d4151fa6b3@googlegroups.com>
Injection-Date: Wed, 11 Oct 2017 22:25:23 -0000 (UTC)
Injection-Info: franka.jacob-sparre.dk;
 posting-host="rrsoftware.com:24.196.82.226";
	logging-data="4317"; mail-complaints-to="news@jacob-sparre.dk"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246
Xref: news.eternal-september.org comp.lang.ada:48431
Date: 2017-10-11T17:25:22-05:00
List-Id: <comp.lang.ada>

"John Smith" <yoursurrogategod@gmail.com> wrote in message 
news:18781206-12b4-4da8-ac8c-96d4151fa6b3@googlegroups.com...
...
> I've had the binary that uses the *.DLL having it include the
> library via the *.gpr file and that used to work.  When it comes
>to finding the DLL, that should be handled by the related GPRs.

No. Loading (seeparate) DLLs is handled by Windows, and you have to follow 
the Window's rules for that. The compiler has nothing to do with it, and 
thus project files have nothing to do with it. This works much like the 
running of any executable -- that's a Windows function, not a 
compiler/linker function.

Several people have suggested that you place the .DLL (temporarily) in a 
place where Windows will always look for it (like System32) to find out 
whether or not it is a loading problem or some compilation problem (where 
further playing with project files will be profitable). I'd suggest doing 
that and (if necessary) providing the results here.

                                     Randy.