Closed
Bug 478159
Opened 16 years ago
Closed 16 years ago
Release Emulator Compatible Builds for Windows Mobile
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
ARM
Windows Mobile 6 Professional
Tracking
(Not tracked)
VERIFIED
WORKSFORME
Future
People
(Reporter: dougt, Assigned: pavlov)
References
Details
After we checked in 477678, our builds no longer work (crash) in the windows device emulator. The change is good (it makes us go faster on ARM11 ARMv6), but it prevents people from using the emulator for testing, development, prototyping, etc.
Right now, there are no emulators from Microsoft that support ARMV5 (only ARMv4 or ARMv5).
It might be a good idea to produce emulator build periodically so that we can support the community.
Reporter | ||
Updated•16 years ago
|
Assignee: nobody → pavlov
Summary: Produce Emulator Compatible Builds for Windows Mobile → Release Emulator Compatible Builds for Windows Mobile
Target Milestone: --- → Future
Comment 2•16 years ago
|
||
Doug, I think we can close this bug since arm cpu type is now detected on run-time.
Reporter | ||
Comment 3•16 years ago
|
||
wfm.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Comment 4•16 years ago
|
||
the upcoming release will work in the emulators. I'm not sure that will remain true.
Reporter | ||
Comment 5•16 years ago
|
||
we can always reopen the bug. (fwiw, i tested with a pull from the tip from a few hours ago)
Comment 6•16 years ago
|
||
(In reply to comment #4)
> the upcoming release will work in the emulators. I'm not sure that will remain
> true.
I have been always testing on emulator, so I can reopen this bug if it fails on emulator.
Comment 7•16 years ago
|
||
running in an emulator works just fine. Issues with available space and memory
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•