My main project relies on 2 libs containing the same config.h file in their own dir. My main issue with Android.mk is that I am unable to specify 2 sets of local includes for each object file. Two ways I can resolve this: 1. Building 2 static libs in each sub-dir, with each Android.mk in their respective sub-dirs pointing to the right config header: > Top Dir: Android.mk builds two static libs >> Sub-DIr A: Android.mk with local header pointing to this dirA >> Sub-DIr B: Android.mk with local header pointing to this dirB
2. Changing the name of each config file (configA.h and configB.h) and building from one Android.mk by adding the two sub-dirs in the local includes. The first method adds complexity to maintaining 2 additional Android.mk, the second one adds complexity in requiring to modify source files and renaming headers. Is there a better way to handle this situation, knowing that in the future, I would also need to have different C_FLAGS specified for each sub-project? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
