Upload pre- and post-ProGuard javap outputs




Firefox for Android
Build Config & IDE Support
4 years ago
2 hours ago


(Reporter: nalexander, Unassigned, Mentored)



Firefox Tracking Flags

(Not tracked)




4 years ago
ckitching suggested using javap to produce and upload reports of the contents of the Fennec namespace pre- and post-Proguard.  It's a nice idea; here's how to do it.

1) First, add code to mobile/android/base/Makefile.in around [1] that uses code like [2] to create two files containing the javap outputs.  A Make function (like aapt_command) that took a list of .jar files would be best, 'cuz we have two lists of .jar files that we want to process (see ALL_JARS and the contents of jars-proguarded).  Call these files pre-Proguard.javap.txt and post-Proguard.javap.txt.

2) Add these files to the libs:: line, and $(INSTALL) them into $(FINAL_TARGET) as well.

3) Add the files to the UPLOAD_EXTRA_FILES in packager.mk around [3].

4) Push a try build, and verify your files got built and uploaded to the build directory.

[1] http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/Makefile.in#392

[2] http://stackoverflow.com/a/1171675

[3] http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/installer/packager.mk#341

Comment 1

4 years ago
This is a reasonable mentored bug, if you're interested in the Mozilla build system; but not a good first bug.
Mentor: nalexander

Comment 2

4 years ago
I am interested to work on it.I am a newbie, can you help please?

Comment 3

4 years ago
(In reply to schhajed.iet from comment #2)
> I am interested to work on it.I am a newbie, can you help please?

Hi!  Thanks for your interest, but unfortunately this is not a good first (or even second) bug.  We always recommend looking at http://www.joshmatthews.net/bugsahoy/?mobile=1&simple=1 for good first bugs that are mentored.

Comment 4

2 hours ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Last Resolved: 2 hours ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.