That shouldn't be necessary. Android Studio uses that structure simply because that structure is a bit more extensible, making it easy to add new modules. However, if all you want is just a single project layout, you can do something like what this test app does:
https://android.googlesource.com/platform/tools/base/+/master/build-system/tests/aidl/ If that doesn't work, please file a bug with a sample project that fails to import in Studio. On Fri, Dec 27, 2013 at 2:53 AM, Roberto Tyley <[email protected]> wrote: > While the gradle-based build system doesn't require it, Android Studio seems > to require a multi-project layout even for simple single-module projects. > The top-level folder has several empty-ish config files: > > build.gradle > gradle.properties > local.properties > settings.gradle > > In terms of source-control, I feel like I'd rather just check the sub-folder > in - that's where everything that's not actually totally generic begins - > but Android Studio can't import a gradle project based just on the project > sub-folder - even though it functions as a gradle build. > > Roberto > > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
