Hi All, On Mon, Sep 23, 2013 at 09:28:44PM +0200, Lukasz Rymanowski wrote: > Hi Marcel, > > On Mon, Sep 23, 2013 at 11:51 AM, Frederic Danis > <frederic.danis@xxxxxxxxxxxxxxx> wrote: > > Hello Marcel, > > > > On 21/09/2013 19:14, Marcel Holtmann wrote: > >> > >> Hi Fred, > >> > >>> Define local mapping to glib path, otherwise this has to be inside > >>> central > >>> place in the build repository. > >>> > >>> Retrieve Bluetooth version from configure.ac. > >>> --- > >>> .gitignore | 2 + > >>> Android.mk | 9 ++++ > >>> Makefile.am | 1 + > >>> Makefile.android | 7 ++++ > >>> android/Android.mk | 24 +++++++++++ > >>> android/main.c | 119 > >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++ > >>> configure.ac | 5 +++ > >>> 7 files changed, 167 insertions(+) > >>> create mode 100644 Android.mk > >>> create mode 100644 Makefile.android > >>> create mode 100644 android/Android.mk > >>> create mode 100644 android/main.c > >> > >> > >> lets split this out a little bit. Code additions should not be intermixed > >> with additions to the build system and especially configure options. > >> > >> I rather not have a top-level Android.mk. It should be enough to provide > >> an android/Android.mk. > > BTW, do you expect to have only one Android.mk for the whole project or > this is OK for you to have smaller Android.mk in different subfolders like > /src/shared etc. Both ways are valid. While having a single huge Android makefile is somehow make sense it would have several disadvantages: - we cannot use local build with "mm" for building for example only tools or libs - Android.mk will become very large and difficult to read Best regards Andrei Emeltchenko -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
