Closed Bug 590112 Opened 14 years ago Closed 13 years ago

Fix Android cross-compiles on FRR

Categories

(Tamarin Graveyard :: Build Config, defect, P3)

x86
Windows XP
defect

Tracking

(Not tracked)

RESOLVED FIXED
Q3 11 - Serrano

People

(Reporter: pnkfelix, Assigned: pnkfelix)

References

Details

Attachments

(1 file, 1 obsolete file)

Steven recently updated his flashruntime-redux (FRR) branch in P4 so that it builds the usual targets.  But there remain incompatibilities between the tip of tamarin-redux (TR) and the Android portion of FRR.  This ticket is intended to track the fixes necessary to TR in order to build and run an Android player.

(There are also patches necessary for FRR itself, but those are not meant to be directly posted here.)
Assignee: nobody → fklockii
(Sorry, I failed to follow proper process on P4 CL 707419 which changes FRR.  Its an obvious fix to a real problem.  But as a fan of proper process, I am ashamed; won't happen again.)

On a semi-related note, we may want to follow up and find out whether the Player's Android build infrastructure should be sym-linked into the makefiles in tamarin-redux, rather than trying to keep these files in sync...
(In reply to comment #1)
> (Sorry, I failed to follow proper process on P4 CL 707419 which changes FRR. 
> Its an obvious fix to a real problem.  But as a fan of proper process, I am
> ashamed; won't happen again.)

(by proper process, I mean "getting another human to review the patch")
This patch was the simplest way to get Android building against FRR.  It is probably not the right thing for the long-term; that is, it probably should not be pushed to the repository.  But I figured it was easiest to upload the patch here so that others who want to target Android can get something going quickly.
works around gcc warning turned error in the Android build.

When I discussed this with Lars some time ago [1], he mentioned the option of disabling the particular warning rather than changing the code to accommodate gcc.

But it really is a pretty simple mod, so maybe we should push it anyway...

[1] http://asteam.corp.adobe.com/irc/log/ttlogger/tamarin/20100818
Status: NEW → ASSIGNED
Flags: flashplayer-triage+
Flags: flashplayer-qrb+
Priority: -- → P3
Target Milestone: --- → flash10.2.x-Spicy
OS: Mac OS X → Windows 7
See Also: → 598422
See Also: → 598424
Comment on attachment 469027 [details] [diff] [review]
kills dead (debug-only) private method

obsoleted by fix for https://bugzilla.mozilla.org/show_bug.cgi?id=598424
Attachment #469027 - Attachment is obsolete: true
The remaining work should be covered by bug 598422.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Bug 598422 was resolved as "wontfix", which does not fix this bug, so I am reopening this bug.

(Tommy is in contact with the Android team about the issue; I'm just keeping notes/patches with this bug and want to keep its state accurate.)
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
is this still in play?
(In reply to comment #8)
> is this still in play?

yes it is, but I do not know how soon it will be resolved.  As recently as Friday (December 3rd), Tommy and Simon and I were chatting about it on the IRC channel.

See: http://asteam.corp.adobe.com/irc/log/ttlogger/tamarin/20101203
and scroll down to 15:55
Target Milestone: flash10.2.x-Spicy → flash10.x-Wasabi
Target Milestone: flash10.x-Wasabi → flash10.x-Serrano
Okay at some point the SetGCToNull went away.  :)
Status: REOPENED → RESOLVED
Closed: 14 years ago13 years ago
OS: Windows 7 → Windows XP
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: