search

deltaluca / nape

Haxe/AS3 Physics Engine
http://napephys.com
Other
542 stars 77 forks source link

ASC2 throw 100 warnings #50

Closed katopz closed 11 years ago

katopz commented 11 years ago

swc release build Milestone 10.1 r15 will throw around 100 warnings via ASC2 in my FB4.7 AIR3.4 e.g.

The definition getClass.T depended on by Type in the SWC release_nape_10.1_r15.swc could not be found

The definition Null.T depended on by flash.Boot in the SWC release_nape_10.1_r15.swc could not be found

The definition Null.T depended on by nape.callbacks.CbTypeList in the SWC release_nape_10.1_r15.swc could not be found

and other 100 warnings about "Null.T"

i'm try asking adobe about this and here is the answer

That release_nape.swc’s catalog.xml does not appear to have been constructed correctly (it looks like it was created by Haxe). Those warnings are real - the defintions in catalog.xml say they have a dependency on a type "T" in a package "Null", but the compiler can’t find it.

The maker of Haxe might have a "built-in" SWC somewhere to provide this definition?

If not, and if the type is not used at runtime, you could for now hack in a Null/T.as source file (and any other missing definition) as an empty class definition to suppress the linkage error, though it would be better if Haxe could correct the catalog.xml in such SWCs.

please advice

deltaluca commented 11 years ago

Posted on haxe mailing list.

deltaluca commented 11 years ago

nightly versions of haxe have already resolved this issue, I'll make sure to update my compiler before releasing next nape version.

uenon commented 11 years ago

ASC2 throw 255 warnings in my FB4.7

The definition Void depended on by flash.Boot in the SWC nape-dev_2.0.3.swc could not be found ...

deltaluca commented 11 years ago

This'll have to wait till I get home from christmas after the new year.

Posted on haxe issues.

deltaluca commented 11 years ago

Recent nightly version of haxe has fixed this. So next release of Nape should hopefuly remove these warnings.

Durss commented 11 years ago

Same here, any chance to see that fixed soon.? :)

deltaluca commented 11 years ago

I've just released 2.0.6 for a bug fix. Could you check if these warnings are now gone too?

Closing for now as I should expect they are.

sthulesen commented 11 years ago

Confirming that the warnings are fixed with 2.0.6

uenon commented 11 years ago

The warnings are gone in my environment.

deltaluca commented 11 years ago

Thanks!