Closed Bug 1385695 Opened 8 years ago Closed 8 years ago

Libraries are always built in "release" config when building the app

Categories

(Firefox Build System :: Android Studio and Gradle Integration, enhancement)

All
Android
enhancement
Not set
normal

Tracking

(firefox57 fixed)

RESOLVED FIXED
mozilla57
Tracking Status
firefox57 --- fixed

People

(Reporter: JanH, Assigned: JanH)

References

Details

Attachments

(1 file)

... which means that debug info for local variables and the like will be missing for files in "geckoview" respectively "thirdparty".
Comment on attachment 8891802 [details] Bug 1385695 - Propagate "app" debug/release build type to dependencies. https://reviewboard.mozilla.org/r/162796/#review171220 Is this helping when using the debugger? The only thing I'm not sure about: When we start to actually publish those artifacts via a maven repository then I do not think we want to publish non release artifacts.
Comment on attachment 8891802 [details] Bug 1385695 - Propagate "app" debug/release build type to dependencies. https://reviewboard.mozilla.org/r/162796/#review171220 When looking at things belonging to Geckoview it definitively helps, so the conflict with the configuration required for Maven is a bit unfortunate. Not doing this wouldn't be a terrible problem for me though to be honest, as I could simply fold these commits into my private base commit I keep around for mass-rebasing of my patches and occasions like this, but of course that wouldn't help anybody else who might want to properly debug geckoview. On the other hand it seems like I might be the first one to complain about this, so make of that what you will :-)
Be aware that release configurations are subtly intertwined with Gecko binaries: http://searchfox.org/mozilla-central/source/mobile/android/gradle/with_gecko_binaries.gradle#22. At the time that I evaluated it, I concluded that it was not feasible to use release configurations in the way you are suggesting. But now I don't see why not, and I support this approach in general. Just be very careful with the Gecko binaries! nechen: I'll wait on the review from Bug 1392537, and let you all agree what is best here.
Flags: needinfo?(cnevinchen)
I think Jan's patch is better :) Thanks for the help to let all library modules debugger friendly :)
Flags: needinfo?(cnevinchen)
Comment on attachment 8891802 [details] Bug 1385695 - Propagate "app" debug/release build type to dependencies. https://reviewboard.mozilla.org/r/162796/#review178624 If this unblocks debugging then this is okay with me. We can reconcider once we actually distribute builds.
Attachment #8891802 - Flags: review?(s.kaspari) → review+
(In reply to Nick Alexander :nalexander [parental leave until September 15th] from comment #5) > Just be very careful with the Gecko binaries! Hmm, I hope this try run is enough of a good sign that this didn't mess up things too badly: https://treeherder.mozilla.org/#/jobs?repo=try&revision=18c89fcebeb8f9b327b8d1084c9bef7ce9e178e6
(In reply to Jan Henning [:JanH] from comment #8) > (In reply to Nick Alexander :nalexander [parental leave until September > 15th] from comment #5) > > Just be very careful with the Gecko binaries! > > Hmm, I hope this try run is enough of a good sign that this didn't mess up > things too badly: > https://treeherder.mozilla.org/#/ > jobs?repo=try&revision=18c89fcebeb8f9b327b8d1084c9bef7ce9e178e6 I triggered the Robocop jobs for moz.build and Gradle -- that actually runs the APK, including trying to load the Gecko binaries. None of the other tests actually start Gecko :)
Pushed by mozilla@buttercookie.de: https://hg.mozilla.org/integration/autoland/rev/2f4ec6a1b39e Propagate "app" debug/release build type to dependencies. r=sebastian
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 57
Product: Firefox for Android → Firefox Build System
Target Milestone: Firefox 57 → mozilla57
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: