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.36.117.83 with SMTP id y80mr3351399itc.48.1507684925336; Tue, 10 Oct 2017 18:22:05 -0700 (PDT) X-Received: by 10.157.0.7 with SMTP id 7mr33659ota.14.1507684925307; Tue, 10 Oct 2017 18:22:05 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.fcku.it!peer01.fr7!futter-mich.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!k70no182829itk.0!news-out.google.com!194ni196itf.0!nntp.google.com!k70no182824itk.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 10 Oct 2017 18:22:05 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2601:18f:900:f900:453d:87a5:de7c:1786; posting-account=AvekzAoAAABj-TclKcOWQmXwA49MFPGX NNTP-Posting-Host: 2601:18f:900:f900:453d:87a5:de7c:1786 References: <9885a3fd-8ffa-4076-ba1f-db2f8035e0dc@googlegroups.com> <15345d32-0610-444e-b611-f480bf60f9f0@googlegroups.com> <93483ae9-c1ec-4cbe-92f9-49eaf41bc1f3@googlegroups.com> <5984e47c-cfe5-4d22-9907-f113f24647b9@googlegroups.com> <2bc424a1-3559-42bb-9f40-22763c21e7f2@googlegroups.com> <761a5a41-04de-4f48-aac2-f5fe167dabd5@googlegroups.com> <41f9bb00-4fa3-472e-98e4-d32e5ae4e2d6@googlegroups.com> <2f235de2-5969-4cf8-ada6-c0d886f0f9ac@googlegroups.com> <2d6225df-f847-4324-a7f0-e4544d0b5b44@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <5d5b30f0-a7da-40d7-b4d7-7e5dcf9417d6@googlegroups.com> Subject: Re: The best possible way to call a function in a shared library From: John Smith Injection-Date: Wed, 11 Oct 2017 01:22:05 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Body-CRC: 2309733139 X-Received-Bytes: 4174 Xref: news.eternal-september.org comp.lang.ada:48422 Date: 2017-10-10T18:22:05-07:00 List-Id: On Tuesday, October 10, 2017 at 9:18:12 PM UTC-4, Anh Vo wrote: > On Tuesday, October 10, 2017 at 5:38:13 PM UTC-7, John Smith wrote: > > On Tuesday, October 10, 2017 at 9:15:13 AM UTC-4, Dmitry A. Kazakov wro= te: > > > On 10/10/2017 05:39, John Smith wrote: > > >=20 > > > > Now, when I try to have my DLL loaded, it gives me an error saying > > > > that it doesn't see it. > > > Check the OS rules about loader search path. > > >=20 > > > --=20 > > > Regards, > > > Dmitry A. Kazakov > > > http://www.dmitry-kazakov.de > >=20 > > I'm assuming that it has something to do with gnatls (sorry, I'm not su= re how this works on Windows.) This did work shortly after I got the stati= c libraries to work (they still do, the shared libraries do not work though= ) and I'm trying to figure out what I screwed up. > >=20 > > This is what I'm seeing when doing gnatls: > >=20 > > > gnatls -v > >=20 > > GNATLS GPL 2016 (20160515-49) > > Copyright (C) 1997-2016, Free Software Foundation, Inc. > >=20 > > Source Search Path: > > > > C:\GNAT\2016\lib\gcc\i686-pc-mingw32\4.9.4\adainclude > >=20 > >=20 > > Object Search Path: > > > > C:\GNAT\2016\lib\gcc\i686-pc-mingw32\4.9.4\adalib > >=20 > >=20 > > Project Search Path: > > > > C:\GtkAda\lib\gnat > > C:\GNAT\2016\i686-pc-mingw32\lib\gnat > > C:\GNAT\2016\i686-pc-mingw32\share\gpr > > C:\GNAT\2016\share\gpr > > C:\GNAT\2016\lib\gnat >=20 > As a quick test, place all *.dll in the question at C:\Windows\System32 >=20 > Anh Vo But it's not searching for those DLLs in there. I could put them into something like "C:\GNAT\2016\lib\gnat", but ultimatel= y that's not what I want.