Re: absolute or relative path for source files

2011-05-15 Thread Ralf Wildenhues
* Vincent Torri wrote on Sun, May 15, 2011 at 09:11:10PM CEST: > Is it better to use absolute path: > > mylib_SOURCES = $(top_builddir)/path1/path2/file.c > > or relative path > > mylib_SOURCES = ../path2/file.c Both can be ok, but it is important that you don't mix both in the same makefile, a

Re: absolute or relative path for source files

2011-05-15 Thread Daniel Herring
On Sun, 15 May 2011, Vincent Torri wrote: in a Makefile.am that is in the "$(top_builddir)/path1/path3" directory, the library uses a file that is in the "$(top_builddir)/path1/path2" directory. Is it better to use absolute path: mylib_SOURCES = $(top_builddir)/path1/path2/file.c or relative p

absolute or relative path for source files

2011-05-15 Thread Vincent Torri
Hey, in a Makefile.am that is in the "$(top_builddir)/path1/path3" directory, the library uses a file that is in the "$(top_builddir)/path1/path2" directory. Is it better to use absolute path: mylib_SOURCES = $(top_builddir)/path1/path2/file.c or relative path mylib_SOURCES = ../path2/file.c ?

Re: Dependecy directory and EXTRA_PROGRAMS

2011-05-15 Thread Ralf Wildenhues
Hi Sergio, * Sergio Belkin wrote on Fri, May 13, 2011 at 05:37:28AM CEST: > I have a directory ./doc/tests of source files as documentation > examples, you can compile optionally issuing "make tests". That files > as marked with dist_ in order to go into distribution. OK. So is there anything wr