Flash Builder 4.7 and old projects


I recently decided to give the beta of Flash Builder 4.7 a try, and found a project I have been working on deciding not to compile.  All kinds of warnings (100+) showed up in my problems panel.  My project relies on a shared project, and for some reason some core files like BitmapAsset and ByteArrayAsset weren’t found.

Class mx.core::BitmapAsset could not be found.

Most google searches only turned up fixes involving the compiler flags ala:

mxmlc -static-link-runtime-shared-libraries=true

This did not fix my problem, what ultimately did though was going to my shared library’s properties, Library Path tab, and setting the combo box in the picture below to Merged into code.

This ended up clearing most errors, a few still remained but weren’t problem. It turns out that HAXE compiled swcs are causing warning to show up relating to missing: getClass.T and Null.t
These omissions don’t seem to be affecting my ability to compile, but that is probably due to the fact that I’m not using the NAPE library which depends on a HAXE compiled swc.

  • Nick Collins

    I’ve been running into a bunch of problems like this for any project that is using the new ASC 2.0 compiler. Particularly with projects that are using Flash IDE compiled SWCs or like in your case, HAXE compiled SWCs.

    *Usually* doing a Project – Clean will resolve the issue for me, at least temporarily, but it is a major annoyance. That and the incompatibility with SourceMate, but that is for ElementRiver to fix, I suppose.