ok so all settings in android.Keys.Android are scoped under the project and settable under settings, hooray
On Wed, Jan 8, 2014 at 5:43 PM, Daniel Skinner <[email protected]> wrote: > this still brings the question of, how does one call `mergeManifests in > Android := false` in a multiproject setup. Simply dropping it in the object > init appears to have no effect. > > > On Wed, Jan 8, 2014 at 5:23 PM, Daniel Skinner <[email protected]> wrote: > >> aah, nvm, this must be internal to the plugin as I forgot to specify my >> libs in project.properties >> >> >> On Wed, Jan 8, 2014 at 5:09 PM, Daniel Skinner <[email protected]> wrote: >> >>> I know there's a number of gists linked to in the README of >>> android-sdk-plugin, but the number of operators in use at times makes my >>> head spin. I'm reading about multi-project builds here >>> http://www.scala-sbt.org/0.13.1/docs/Getting-Started/Multi-Project.html and >>> have setup the following build.scala per my liking >>> >>> object MyProjectBuild extends Build { >>> >>> lazy val root = Project(id = "MyProject", base = file(".")) settings >>> (common ++ Seq( >>> libraryDependencies ++= Seq( >>> "com.android.support" % "appcompat-v7" % "19.0.0", >>> "com.github.chrisbanes.actionbarpulltorefresh" % "extra-abc" % "+" >>> ) >>> ): _*) dependsOn(slidingMenu, pullToRefresh) aggregate(pullToRefresh, >>> slidingMenu) >>> >>> lazy val slidingMenu = Project(id = "SlidingMenu", base = >>> file("libraries/SlidingMenu")) settings (common: _*) >>> lazy val pullToRefresh = Project(id = "PullToRefresh", base = >>> file("libraries/PullToRefresh")) settings (common: _*) >>> >>> lazy val common = android.Plugin.androidBuild ++ Seq( >>> scalacOptions in Compile ++= Seq("-deprecation", "-feature"), >>> javacOptions in Compile += "-deprecation" >>> ) >>> >>> } >>> >>> This does compile the libs and I'd assume exposes the classpath, but I'm >>> unsure of how to get the resources from the library projects merged. As the >>> user here, I'd be looking for a cousin to dependsOn and aggregrate. >>> >>> From the outdated wiki example at >>> https://github.com/pfn/android-sdk-plugin/wiki/Working-with-Android-library-projects >>> it >>> seems like maybe the "compile in Compile ..." line is responsible >>> >>> lazy val appSettings = AndroidSdkPlugin.androidBuildSettings :+ >>> (name := "myawesomeapp") :+ >>> (compile in Compile <<= compile in Compile >>> dependsOn(packageT in Compile in menuDrawerLibrary)) >>> >>> Is that the case? If this is standard sbt stuff in use to make this >>> work, any standard reading in the sbt docs (ok its all standard reading but >>> any direct links on the subject) is appreciated. >>> >>> I've seen references to AutoLibraryProjects as well but only in the >>> context of a build.sbt file, and I'm unsure of how to use this in the >>> context of a build.scala multiproject setup. >>> >>> Thanks, >>> Daniel >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "scala-on-android" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/scala-on-android/MGP4LnXMN1A/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, 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 "scala-on-android" 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.
