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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.107.161.77 with SMTP id k74mr10802642ioe.66.1509949549487;
        Sun, 05 Nov 2017 22:25:49 -0800 (PST)
X-Received: by 10.157.20.173 with SMTP id d42mr529010ote.3.1509949549423; Sun,
 05 Nov 2017 22:25:49 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.linkpendium.com!news.linkpendium.com!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!k70no855709itk.0!news-out.google.com!p6ni1681itp.0!nntp.google.com!l196no860635itl.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sun, 5 Nov 2017 22:25:49 -0800 (PST)
In-Reply-To: <307494b9-c79d-4e8a-887c-3a588374b082@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=2601:191:8303:2100:5985:2c17:9409:aa9c;
 posting-account=fdRd8woAAADTIlxCu9FgvDrUK4wPzvy3
NNTP-Posting-Host: 2601:191:8303:2100:5985:2c17:9409:aa9c
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>
 <orm5oj$46t$1@franka.jacob-sparre.dk>
 <307494b9-c79d-4e8a-887c-3a588374b082@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d9b17da4-ae10-4bb3-9d9e-7bb5b6625204@googlegroups.com>
Subject: Re: The best possible way to call a function in a shared library
From: Robert Eachus <rieachus@comcast.net>
Injection-Date: Mon, 06 Nov 2017 06:25:49 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: news.eternal-september.org comp.lang.ada:48727
Date: 2017-11-05T22:25:49-08:00
List-Id: <comp.lang.ada>

On Wednesday, October 11, 2017 at 6:57:35 PM UTC-4, John Smith wrote:
> Putting the DLL file into the same directory as the executable will cause the binary to run as it should.
> 
> Putting the same DLL into C:\Windows\System32 gives me the exception that the DLL in question cannot be found.
> 

What happens if you put the .dll in C:\Windows\SysWOW64 That would imply that you are creating (or looking for) a 64-bit DLL.