Hi, OK, never mind, problem solved. It seems that $(top_srcdir) simply did not expand anymore in _SOURCES. Keeping my structure with the build/Makefile.am but replacing $(top_srcdir) with '..' did the trick, it works like a charm now, including in and out of tree builds.
No more warnings, no more not found .Po files, and I get my binaries and libraries nicely in the build directory without polluting the source tree. Kind regards, Jin On Sun, Sep 01, 2013 at 06:45:32PM +0200, Sergey 'Jin' Bostandzhyan wrote: > Hi, > > thanks for your reply, some more questions though: > > On Sun, Sep 01, 2013 at 03:08:37PM +0100, Diego Elio Pettenò wrote: > > Is it possible to keep the logic with the in-tree build directory with > > automake 1.14? I did try to move all the logic from build/Makefile.am > > into > > the top level Makefile.am and removing build/Makefile.am completely, but > > it does not help - .Plo files are not found. > > > > > > I'd say it's a very bad idea to use that build/Makefile.am. > > Could you please elaborate? I'd be interested in the technical details on why > it is a bad idea? > > > Move the includes on the top-level Makefile.am, and get rid of > > $(top_srcdir) on > > all the _SOURCES declaration and it should work fine. > > It does compile now, and it does dump all the .o and .lo and what not > in the same directory as the sources - very ugly. This is exactly what I was > avoiding with the separate build directory and it worked just perfectly > until automake 1.14 came along. > > Is there any way to tell 1.14 to place the object files into some dedicated > directory without doing an actual "out of tree" build, or in other words, > can I achieve the same setup that I had on 1.14 somehow? > > Kind regards, > Jin >