Re: The best possible way to call a function in a shared library

[John Smith <yoursurrogategod@gmail.com>]

On Wednesday, October 11, 2017 at 3:08:16 AM UTC-4, Dmitry A. Kazakov wrote:
> On 11/10/2017 02:38, John Smith wrote:
> 
> > I'm assuming that it has something to do with gnatls (sorry, I'm not
> > sure how this works on Windows.) This did work shortly after I got the
> > static libraries to work (they still do, the shared libraries do not
> > work though) and I'm trying to figure out what I screwed up.
> 
> Static libraries are linked statically. DLLs are linked at run-time by 
> the system loader. There are rules where the loader looks for the DLLs.
> 
> Under Windows they are:
> 
> https://msdn.microsoft.com/en-us/library/windows/desktop/ms682586(v=vs.85).aspx
> 
> P.S. The simplest way is to put the executable in the same directory 
> with the DLL.
> 
> -- 
> Regards,
> Dmitry A. Kazakov
> http://www.dmitry-kazakov.de

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.

This compiles the *.exe:

with "../../../use_project.gpr";

project Main_Dynamic is
  for Source_Dirs use (".");
  for Object_Dir use ".";
  for Main use ("main_dynamic.adb");

  package Builder is
  end Builder;

  package Compiler is
    for Switches("Ada") use ("-g", "-gnatwa");
  end Compiler;

  package Binder is
  end Binder;

  package Linker is
  end Linker;
end Main_Dynamic;




And this is what points to the compiled DLL (but doesn't compile it):

library project Use_Project is
  for Externally_Built use "true";
  for Source_Dirs use ("src");
  for Library_Dir use "bin/debug";
  for Library_Name use "simpleLibs";
  for Library_Kind use "dynamic";
  for Library_ALI_Dir use "ali/debug";
end Use_Project;