https://bugs.freedesktop.org/show_bug.cgi?id=69874
--- Comment #7 from Emil Velikov <emil.l.veli...@gmail.com> --- (In reply to comment #6) > bin_PROGRAMS = abc > abc_SOURCES = sub/main.c sub/abc.c > > When you set subdir-objects, it always creates object files in the same dir > as the source file. E.g: sub/main.o, sub/abc.o > AFAICS slapping subdir-objects within configure.ac is not an option(at least not currently) > So, its working as expected, however this is BROKEN when I configure under a > different directory. Eg: mkdir config1; cd config1; ../configure. I expect > all *.o in a parallel hierarchy under config1, but with subdir-objects it is > still creating object files alongside the source. Something seems to be broken in your setup. subdir-object should work with out of tree builds, and it seems to work great on my system (recent(ish) master + subdir-object branch) $ cd mesa && mkdir automake-build && cd automake-build $ ../autogen.sh && make $ cd ../ $ find . -name "*.so" -or -name "*.la" -or -name "*.a" -or -name "*.o" | grep -v automake\-build | wc -l 0 $ git clean -nxd | grep -v Makefile\.in Would remove aclocal.m4 Would remove autom4te.cache/ Would remove automake-build/ Would remove bin/* Would remove configure Would remove m4/* Would remove src/gallium/auxiliary/util/*.pyc Would remove src/mapi/glapi/gen/*.pyc Would remove src/mesa/main/get_hash_params.pyc With dricore gone I can revisit/update my branch and get some of the autoconf/automake spam out of the way :) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev