On 08/11/11 22:57, Chris Frey wrote: > If you can somehow adjust Android's build system to make sure that all > system directories are listed first, and that all Barry headers must > be included via <barry/...>, then this shouldn't be a problem. Is this > possible?
Yes, turns out it is possible. Thanks for the suggestion. I've fixed my github branch at git://github.com/tobygray/barry.git to contain your various suggestions and fixes. The only changes that I'm not entirely sure about now are the use of Makefile.am. Currently the various files to include in the distribution tarball are specified by using a Makefile.am in the android directory. However this has a couple of consequences: 1) When running make from the top level, make will recurse into the android directory. There are no default targets, but it's possibly a little ugly that you see android mentioned in make output, even when not building for it. 2) When you do want to build for android you have to cd into barry/android and run "make android-binaries". Can you think of a good way of being able to maintain a list of EXTRA_DIST files, yet not have make recurse into an Android directory? Or are you happy with it the way it currently is? Regards, Toby ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
