Hi, Thanks, this works.
Is there also a way to automatically (re)build '../mylib.la' when I issue 'make' in 'lib/python/'? -- Sylvain On Sun, Oct 12, 2008 at 01:21:39PM -0500, Thomas Epperson wrote: > Try placing this in the makefile.am for the lib folder. > SUBDIRS = . python > > That should cause the directories to be entered in the order specified. > > On Sun, Oct 12, 2008 at 1:12 PM, Sylvain Beucler <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I have the following layout: > > lib/ > > lib/Makefile.am > > lib/mylib.la > > lib/python/ > > lib/python/Makefile.am > > lib/python/_pymylib.la > > > > When building, 'make' enters 'lib/python/' first without building > > 'mylib.la'. Since '_pymylib.la' depends on it, compilation fails. > > > > > > Another example: I have a similar issue with gnulib: > > gnulib/ > > gnulib/lib/ > > gnulib/lib/Makefile.am > > gnulib/lib/gnulib.a > > src/ > > src/Makefile.am > > src/myprog > > > > where I couldn't find a way to build 'gnulib.a' first if typing 'make' > > directly from 'src/' (though in this case, typing 'make' at > > $top_builddir usually build things in the right order). > > > > > > I tried a number of tricks but I didn't find a clean solution for > > this. > > > > > > So what is the proper way to tell automake to build a local library > > that is located in a different directory of the same source package > > _before_ building the current directory? > > > > > > Thanks! > > > > -- > > Sylvain > > > > > >
