Thank you for investigating further!
Googling No projects in this build have build file, I found the archive topic.
Here is the example from there:
gradle -c ../settings.gradle -b build2.gradle ear
- What went wrong:
Could not select the default project for this build. No projects in this build have build file ‘build2.gradle’.
And the comment on the issue:
‘-b’ only works for single-project builds, but apparently you have a multi-project build. In that case, only ‘settings.gradle’ decides which build scripts are used, and conditionally using either ‘build.gradle’ or ‘build2.gradle’ is not a recommended approach.
In my example Tegra uses the following command line to execute Gradle:
"C:\...\gradle\gradle-2.2\bin\gradle.bat -i -b C:\...\TegraGradle\Tegra-Android\Debug\build\nsight_tegra_build.gradle assembleDebug -c C:\...\TegraGradle\settings.gradle "
So, it seems that -b option is literally nailed down, and we can’t currently build mutli-project builds in Tegra. :(