-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow debugging AIR target. #849
Comments
See PR #897. AIR support is only available through older versions of openFL (unless it's been added back into Lime recently). It also requires that the debug configuration be correctly and specifically set up; there's nothing automated there. Using AIR APIs will require a haxelib that has the appropriate exports. |
Actually, it looks like Lime has added AIR support back in as of version 5.4.0:
|
Hey Eric, the issue I was having as of 7/7/18 wasn’t with AIR support per se, but with the debugger not launching for an AIR project. I have not restested since, but the issue was as follows: When I run or test a sample app as Flash it opens in the Flash Player Debugger, as expected. If I target AIR and Run, it opens ADL, which is also what I would expect. If I target AIR and Debug, it throws the error: “You can debug only flash or HXCPP targets!” |
Right. The PR addresses that by checking if the OpenFL target was AIR and allowing the debug attempt to go forward; it treats AIR as a flash target, but doesn't do anything else special. If you have installed ADL already and point to that as your "Flex SDK for flash applications debugging," then it should work. Since the change has been approved, I'm going to merge it and you can test the "nightly" build when you get a chance. |
Fixed by #897. And, BTW, the reason that this is tied to OpenFL is that it's the only system that outputs AIR targets right now. The Haxe compiler (currently at 4.0.preview.5) doesn't create AIR targets. |
Ah, got it. I’ll give it a try soon. Thanks for looking into it! |
Hey Eric,
Just did a simple test and it works. Thanks for fixing it!
- Patrick
… On Dec 22, 2018, at 11:11 AM, Eric Bishton ***@***.***> wrote:
Right. The PR addresses that by checking if the OpenFL target was AIR and allowing the debug attempt to go forward; it treats AIR as a flash target, but doesn't do anything else special. If you have installed ADL already and point to that as your "Flex SDK for flash applications debugging," then it should work.
Since the change has been approved, I'm going to merge it and you can test the "nightly" build when you get a chance.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#849 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHOXmKaCGGQR2RG5Iu2Er-Tvf5iI5KbBks5u7lnDgaJpZM4VGcyI>.
|
Received this email:
I think that we simply need to update the test that puts out that message and stops debugging. I use the Adobe AIR debugger when testing flash targets, so this configurattion should work.
The text was updated successfully, but these errors were encountered: