Chad Versace <chad.vers...@linux.intel.com> writes: > Taking the Android.mk's out of Mesa without replacing them with an > Androgenizer-like tool would impose that insufferable situation on > the Android developers.
I certainly wasn't proposing that.
What I would like to do is to eliminate as much of the duplicated
information as possible to make things less fragile. The Androgenizer
tool you mentioned sounds very useful in this context, and it seems like
it would be worth spending some time to improve it if necessary so that
it could be used for Mesa.
Another approach, (and something we did for the cairo project), would be
to put things like lists of filenames needed for the build into a simple
file that could be included by either Makefile.am or Android.mk. That
would at least eliminate one source of duplication.
For example, see this Makefile.sources in the cairo tree:
http://cgit.freedesktop.org/cairo/tree/src/Makefile.sources
This is turn gets included by both the Makefile.am as well as the
Makefile.win32. So cairo does have two parallel trees of Makefiles, but
at least things like filename lists are shared in a single place.
With both Android and automake targeting a common "make" tool, there
should be an opportunity to do even more sharing than cairo is able to
do, (where the Makefile.win32 is aimed at a fairly-incompatible make
tool on Windows).
Chad, you and I should probably talk more in person the next time we're
in the office together.
In the meantime, the patch series that initiated this conversation adds
a Makefile.am to the src/mesa/drivers/dri/common/xmlpool to generate an
options.h file, (one of those complex case you mentioned of using a
local python program to generate some code).
Can you contribute whatever changes are necessary to Android.mk files so
that I could push this series?
Thanks,
-Carl
--
carl.d.wo...@intel.com
pgpLT8HtJQqJh.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
