Closed
Bug 918337
Opened 11 years ago
Closed 4 years ago
Adding a new generated jni method doesn't provide good error logging
Categories
(Firefox for Android Graveyard :: General, defect, P5)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: wesj, Unassigned)
References
Details
I added a new generated JNI method to GeckoAppShell today. Building with 'mach build' gave an error that the method didn't exist. After a bit, I tried just building mobile/android to see if it would fix the problem (using 'make -C mobile/android') and finally saw a 'run this command' message (why do we not just do that for you?). Running that seems to have made the world happy. This should all just work with no intervention.
Comment 1•11 years ago
|
||
We shouldn't run the command automatically because it potentially clobbers local changes if you have any. But I do agree that the full error message should show up when you run mach build; I don't know why that is different from make -C mobile/android. CC'ing ckitching and gps.
Comment 2•11 years ago
|
||
Indeed. It's a bit of a kludge. The procedure that works is to annotate the new method in Java, run a build, copy the generated files, then add your C++ code that uses the new C++ method, then build again. This isn't obvious.
Comment 3•6 years ago
|
||
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
Comment 4•4 years ago
|
||
Post Bug 1453417, I think this is no longer an issue.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•