jamesmgreene / grunt-mxmlc

A Grunt task plugin to compile Adobe Flex/ActionScript/MXML/FLV/etc. apps with the `mxmlc` compiler from the Apache/Adobe Flex SDK.

Hello! I'm James. 👋

I am a "seasoned" software engineer, currently working for GitHub on Actions, Pages, deployments, and more.

About me

• Pronouns: he/him
• Husband to my wife. 🤵‍♂️ 👰‍♀️
• Father to my daughter. 🧒
• Servant to my cats. 🐱 🐈
• Ally. 🏳️‍🌈 🏳️‍⚧️ 🖤 🤎 ❤️ 🧡 💛 💚 💙 💜 🤍
• Open source enthusiast. 💝
• Lifelong learner. 📚
• Scuba diver, traveler, nature enthusiast, hiker, camper, explorer. 🥾
• Handy but willing to admit my limits. 🛠️

grunt-mxmlc's Issues

Compiler error running mxmlc task under Mac OS Mavericks

Error: Command failed: Error: This Java instance does not support a 32-bit JVM.
>> Please install the desired version.

rawConfig options must always be set

Currently, it's mandatory to set rawConfig or the mxmlc task will throw and error.

This is due to var cmdLineOpts = options.rawConfig.split(/\s+/g); which always needs rawConfig to be set.

Add option to strip date metadata out of SWF

Incremental builds (mxmlc -incremental) do not work cross-platform. This problem is not specific to this wrapper (grunt-mxmlc), just a general problem with mxmlc.

e.g. http://stackoverflow.com/questions/5632318/mxmlc-generates-different-binary-on-same-source

One of the answers in that Q&A (and other blog posts around the web) suggest that this is because the SWF is produced with compile-time timestamps added in 2 places, so they must be removed to create identical SWFs. This change would NOT make the incremental builds work correctly but it will result in consistent SWF files when re-running the build over the same source files.

More info around these tags and how to remove them:

• http://wahlers.com.br/claus/blog/undocumented-swf-tags-written-by-mxmlc/
• https://gist.github.com/claus/594367
• https://bugs.launchpad.net/swfmill/+bug/695468
• https://github.com/laomoi/cleanSWF

flex-sdk dependency broken?

I just installed grunt-mxmlc into a blank npm module using npm i --save grunt-mxmlc. For some reason, it insisted on installing [email protected] rather than the latest version. Moreover, when I tried to make it install version 4.6.0-0, I got this:

C:\tmp\temp>npm i --save [email protected]
[installation of [email protected] redacted]
npm ERR! peerinvalid The package flex-sdk does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants flex-sdk@>= 3.0.0-0

If I'm interpreting that error correctly, npm seems to think 4.6.0-0 is lower than 3.0.0-0.

I'm convinced this behavior changed recently. I have a bunch of projects that use grunt-mxmlc and none of them contain an old Flex SDK. Did something change in the way npm and/or semver handles >=?

This is on Windows with node v0.10.31 (on nodist) with npm v2.1.2.

mxmlc path: undefined on osx

flexSdk.bin.mxmlc is undefined, it seems to be looking for it in flex-sdk/lib/flex-sdk/bin which doesn't exist. Is this correct?