There's always the possibility that it is an Adobe bug!

On 2010-06-03, at 15:35, Henry Minsky wrote:

> Also, we almost certainly do want to be having our new apps load the flex
> runtime shared libraries, because the
> text layout engine and framework libraries are pretty large, and it seems
> dumb to have them linked statically, unless there's some reason to believe
> that those libs will not be present in Flash 10 client installs by default.
> How do we find out whether that's the case?
> 
> 
> So we need to figure out how to make the preloader work properly with the
> updated flex compiler.
> 
> 
> On Thu, Jun 3, 2010 at 3:28 PM, Henry Minsky <[email protected]> wrote:
> 
>> OK, so the flex compiler was helpfully trying to tell me what was wrong,
>> but i was not looking at it's error output, since the SWF9External driver
>> seems to just discard it.
>> 
>> The flex compiler said
>> 
>>     [java] Stray error string from external compiler:
>> /private/var/folders/xh/xhmdrA41HCKjjiditeqN1k+++TI/-Tmp-/lzswf9/build/explore-nav/LzPreloader.as:
>> Warning: This compilation unit did not have a factoryClass specified in
>> Frame metadata to load the configured runtime shared libraries. To compile
>> without runtime shared libraries either set the
>> -static-link-runtime-shared-libraries option to true or remove the
>> -runtime-shared-libraries option.
>> 
>> 
>> And so I added in  "-static-link-runtime-shared-libraries"  to the compiler
>> command line, and it
>> worked.
>> 
>> So they question remains, why does the Preloader cause the runtime to
>> instantiate something from the
>> "mx.core" package, and why did it not used to do that in earlier version of
>> the flex compiler and
>> framework .swc libs.
>> 
>> 
>> 
>> 
>> 
>> 
>> On Thu, Jun 3, 2010 at 1:23 PM, Henry Minsky <[email protected]>wrote:
>> 
>>> I downloaded a much more recent flex compiler milestone build (March 2010,
>>> flex_sdk_4.0.0.14159)
>>> in order to get the updated Text Layout Framework class libraries, as well
>>> as numerous compiler
>>> fixes.
>>> 
>>> However, when I compile an app now, and try to run it, I get this error
>>> during startup
>>> 
>>> VerifyError: Error #1014: Class mx.core::MovieClipLoaderAsset could not be
>>> found.
>>> 
>>>    at flash.display::MovieClip/nextFrame()
>>>    at
>>> LzPreloader/enterFrame()[/Users/hqm/openlaszlo/lib/jakarta-tomcat-5.0.30/temp/lzswf9/Users/hqm/openlaszlo/trunk2/test/tlf/build/edit/LzPreloader.as:20]
>>> 
>>> 
>>> Something in the preloaded is trying to reference a class that we don't
>>> have compiled into the app?
>>> 
>>> Does this ring a bell with anyone?
>>> 
>>> note, the preloader code lives in
>>> WEB-INF/lps/lfc/kernel/swf9/LzPreloader.as, but a copy of it that actually
>>> gets inserted into the
>>> app is hardcoded into SWF9Writer#makeApplicationPreamble
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Henry Minsky
>>> Software Architect
>>> [email protected]
>>> 
>>> 
>>> 
>> 
>> 
>> --
>> Henry Minsky
>> Software Architect
>> [email protected]
>> 
>> 
>> 
> 
> 
> -- 
> Henry Minsky
> Software Architect
> [email protected]


Reply via email to