Defining the invocation of a shell command in a gpr project file

Defining the invocation of a shell command in a gpr project file

[David Pereira]

Hi all,

I believe this is a naive question, but still I was not able to find the answer by the google method :-)

So, my question is this: is it possible to invoke a shell command when using gnatmake or gprbuild? I am implementing a binding to C library and, since I am in Mac Os, I have to call the command install_name_tool to change the path point to where the library I am using is available, after the binary is compiled and linked.

Thanks in advance.

Cheers,
David

Re: Defining the invocation of a shell command in a gpr project file

[Simon Wright]

David Pereira <dmrpereira@gmail.com> writes:

> I believe this is a naive question, but still I was not able to find
> the answer by the google method :-)

This aspect of Mac OS X is one of its black mysteries ..

> So, my question is this: is it possible to invoke a shell command when
> using gnatmake or gprbuild? I am implementing a binding to C library
> and, since I am in Mac Os, I have to call the command
> install_name_tool to change the path point to where the library I am
> using is available, after the binary is compiled and linked.

I think you can get away with using -rpath; see the last few paras of
the dyld(1) man page, online at [1], as pointed out to me in a comment
on [2].

You could try

   package Linker is
      for Linker_Options use
        ("-L/path/to/c/lib",
         "-lclib",
         "-rpath",
         "/path/to/c/lib");
   end Linker;

[1]
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/dyld.1.html
[2] http://stackoverflow.com/a/21348716/40851

Re: Defining the invocation of a shell command in a gpr project file

[David Pereira]

Hi Simon,

Unfortunately it does not work. I have tried it already before posting here (maybe I should have mentioned it), and thus the reason to try to understand if there is some GPR black-magic that allows me to explicitly call the install_name_tool from a gpr file.

Thanks anyways for the information you provided.

Cheers,
David

Re: Defining the invocation of a shell command in a gpr project file

[Simon Wright]

Simon Wright <simon@pushface.org> writes:

> David Pereira <dmrpereira@gmail.com> writes:

>> So, my question is this: is it possible to invoke a shell command when
>> using gnatmake or gprbuild? I am implementing a binding to C library
>> and, since I am in Mac Os, I have to call the command
>> install_name_tool to change the path point to where the library I am
>> using is available, after the binary is compiled and linked.
>
> I think you can get away with using -rpath; see the last few paras of
> the dyld(1) man page, online at [1], as pointed out to me in a comment
> on [2].
>
> You could try
>
>    package Linker is
>       for Linker_Options use
>         ("-L/path/to/c/lib",
>          "-lclib",
>          "-rpath",
>          "/path/to/c/lib");
>    end Linker;

Turns out there's more to it than that. I've written up my
investigations at [1]; the key was that the C dylib needs to have an
@rpath in its name too.

Well, it works for me. Hope it helps you.

[1] http://forward-in-code.blogspot.co.uk/2014/02/c-libraries-and-runpath.html

Re: Defining the invocation of a shell command in a gpr project file

[David Pereira]

Great post man! :-)

Thanks a lot!

Cheers,
David

Sexta-feira, 14 de Fevereiro de 2014 17:46:41 UTC, Simon Wright escreveu:
> Simon Wright <simon@pushface.org> writes:
> 
> 
> 
> > David Pereira <dmrpereira@gmail.com> writes:
> 
> 
> 
> >> So, my question is this: is it possible to invoke a shell command when
> 
> >> using gnatmake or gprbuild? I am implementing a binding to C library
> 
> >> and, since I am in Mac Os, I have to call the command
> 
> >> install_name_tool to change the path point to where the library I am
> 
> >> using is available, after the binary is compiled and linked.
> 
> >
> 
> > I think you can get away with using -rpath; see the last few paras of
> 
> > the dyld(1) man page, online at [1], as pointed out to me in a comment
> 
> > on [2].
> 
> >
> 
> > You could try
> 
> >
> 
> >    package Linker is
> 
> >       for Linker_Options use
> 
> >         ("-L/path/to/c/lib",
> 
> >          "-lclib",
> 
> >          "-rpath",
> 
> >          "/path/to/c/lib");
> 
> >    end Linker;
> 
> 
> 
> Turns out there's more to it than that. I've written up my
> 
> investigations at [1]; the key was that the C dylib needs to have an
> 
> @rpath in its name too.
> 
> 
> 
> Well, it works for me. Hope it helps you.
> 
> 
> 
> [1] http://forward-in-code.blogspot.co.uk/2014/02/c-libraries-and-runpath.html