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.4.141 with SMTP id 135mr12694125ioe.101.1507083015302; Tue, 03 Oct 2017 19:10:15 -0700 (PDT) X-Received: by 10.157.39.194 with SMTP id c60mr280012otb.6.1507083015264; Tue, 03 Oct 2017 19:10:15 -0700 (PDT) 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!v62no3850338itd.0!news-out.google.com!194ni6194itf.0!nntp.google.com!v62no3846558itd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 3 Oct 2017 19:10:15 -0700 (PDT) In-Reply-To: <2bc424a1-3559-42bb-9f40-22763c21e7f2@googlegroups.com> 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> <977c48e8-6b5b-4b0e-84a9-cd6447a9ddc3@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> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <27c92481-37ec-431a-8313-edc1b0b5e6ac@googlegroups.com> Subject: Re: The best possible way to call a function in a shared library From: John Smith Injection-Date: Wed, 04 Oct 2017 02:10:15 +0000 Content-Type: text/plain; charset="UTF-8" Xref: news.eternal-september.org comp.lang.ada:48335 Date: 2017-10-03T19:10:15-07:00 List-Id: On Tuesday, October 3, 2017 at 7:28:06 PM UTC-4, John Smith wrote: > On Tuesday, October 3, 2017 at 9:43:52 AM UTC-4, Dmitry A. Kazakov wrote: > > On 2017-10-03 13:32, John Smith wrote: > > > > > I've tried to include the source like so, but keep getting the above error that I posted earlier: > > > > > > gnatmake main_static.adb -largs -aI../../../src -L../../../bin/debug -lsimpleLibs > > > > The switch -I is not for linker, it is for compiler! > > > > gnatmake -I../../../src > > main_static.adb > > -largs -L../../../bin/debug -lsimpleLibs > > > > -- > > Regards, > > Dmitry A. Kazakov > > http://www.dmitry-kazakov.de > > Hi again, > > I did what you suggested and this is the error that I'm getting now: > > gnatmake : gnatmake: could not find the main ALI file > At line:1 char:1 > + gnatmake -l../../../src .\main_static.adb -largs -L../../../bin/debug ... > + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + CategoryInfo : NotSpecified: (gnatmake: could...e main ALI file:String) [], RemoteException > + FullyQualifiedErrorId : NativeCommandError > > Why do the ALI files matter? Aren't the definitions in the *.ads files? Are the *.o file needed as well? Also, I've tried this and got the following result: $ gnatmake -l../../../src main_static.adb -A../../../ali/debug -largs -L../../../bin/debug -lsimpleLibs gnatmake : gnatmake: missing source directory name At line:1 char:1 + gnatmake -l../../../src main_static.adb -A../../../ali/debug -largs - ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (gnatmake: missing source directory name:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError Now the complaint is about the lack of a source file... *sigh*