RE: LDADD doesn't work as expected

2015-09-21 Thread Arthur Schwarz
 

Thanks to all. The suggestion by Thomas won the day. May I say thanks and
assure you that your suspicion is fact.

 

Thanks

art

  _  

From: Thomas Martitz [mailto:ku...@rockbox.org] 
Sent: Monday, September 21, 2015 8:57 AM
To: Bob Friesenhahn; Arthur Schwarz
Cc: automake@gnu.org
Subject: Re: LDADD doesn't work as expected

 

The make target refers to a directory (trailing slash). I suspect the
Makefile.am has a typo.



Am 21. September 2015 17:21:46 MESZ, schrieb Bob Friesenhahn
:

On Mon, 21 Sep 2015, Arthur Schwarz wrote:






 I'm trying to use LDADD to reference libgslip.a in another directory. After


 building libgslip.a with make, I issue a make check and get the message:





 *** No rule to make target '../libgslip/libgslip.a/', needed by


 'SlipTest.exe'.  Stop.





 The test directory is entered and the Makefile in the test directory is


 executed, so the path would seem to be correct but I am missing something.
I


 have read Section 8.1.2 Linking the program and I think I'm following the


 example given, but alas, it just doesn't work.





 I have tried to use LDADD and prog_LDADD with the same effect.



Did you mean to use LIBADD?





It may be wise to construct full paths based on Automake-provided 


variables like
$(top_builddir) rather than using relative paths.





Bob


Re: LDADD doesn't work as expected

2015-09-21 Thread Thomas Martitz
The make target refers to a directory (trailing slash). I suspect the 
Makefile.am has a typo.


Am 21. September 2015 17:21:46 MESZ, schrieb Bob Friesenhahn 
:
>On Mon, 21 Sep 2015, Arthur Schwarz wrote:
>
>>
>>
>> I'm trying to use LDADD to reference libgslip.a in another directory.
>After
>> building libgslip.a with make, I issue a make check and get the
>message:
>>
>> *** No rule to make target '../libgslip/libgslip.a/', needed by
>> 'SlipTest.exe'.  Stop.
>>
>> The test directory is entered and the Makefile in the test directory
>is
>> executed, so the path would seem to be correct but I am missing
>something. I
>> have read Section 8.1.2 Linking the program and I think I'm following
>the
>> example given, but alas, it just doesn't work.
>>
>> I have tried to use LDADD and prog_LDADD with the same effect.
>
>Did you mean to use LIBADD?
>
>It may be wise to construct full paths based on Automake-provided 
>variables like $(top_builddir) rather than using relative paths.
>
>Bob
>-- 
>Bob Friesenhahn
>bfrie...@simple.dallas.tx.us,
>http://www.simplesystems.org/users/bfriesen/
>GraphicsMagick Maintainer,http://www.GraphicsMagick.org/


Re: LDADD doesn't work as expected

2015-09-21 Thread Bob Friesenhahn

On Mon, 21 Sep 2015, Arthur Schwarz wrote:




I'm trying to use LDADD to reference libgslip.a in another directory. After
building libgslip.a with make, I issue a make check and get the message:

*** No rule to make target '../libgslip/libgslip.a/', needed by
'SlipTest.exe'.  Stop.

The test directory is entered and the Makefile in the test directory is
executed, so the path would seem to be correct but I am missing something. I
have read Section 8.1.2 Linking the program and I think I'm following the
example given, but alas, it just doesn't work.

I have tried to use LDADD and prog_LDADD with the same effect.


Did you mean to use LIBADD?

It may be wise to construct full paths based on Automake-provided 
variables like $(top_builddir) rather than using relative paths.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/



LDADD doesn't work as expected

2015-09-21 Thread Arthur Schwarz


I'm trying to use LDADD to reference libgslip.a in another directory. After
building libgslip.a with make, I issue a make check and get the message:

 *** No rule to make target '../libgslip/libgslip.a/', needed by
'SlipTest.exe'.  Stop.

The test directory is entered and the Makefile in the test directory is
executed, so the path would seem to be correct but I am missing something. I
have read Section 8.1.2 Linking the program and I think I'm following the
example given, but alas, it just doesn't work.

I have tried to use LDADD and prog_LDADD with the same effect. 
 
Maintenance turns design into chaos