Hello Steve!
Yes, intrinsic headers generation is very useful too. But -rb_export_included_classes option will allow to manage some cases which can't be done with asigen. For example you have a project and a part of your classes are included to DLLs and another part uses this DDLs. So actually some classes from your sources must be compiled into main app and some not since it will be loaded at run-time later. Since all classes could be located under the same package, generating intrinsic headers won't help because you need to generate intrinsic headers only for classes which will be in DLL.
Regards,
Igor
On 2/23/06, Steve Webster <[EMAIL PROTECTED]> wrote:
Hi Guys,
> >So this is the similar to "-rb_list_included_classes" but outputs compiled
> >classes into specified file instead of standard output device (stdout)?
You might be interested in my asigen project
(http://osflash.org/asigen) which will parse your ActionScript 2.0
files and generate instrinsic versions of them. This was designed to
enable modules to be compiled for a main application (and against the
main application classes) without having to generate a big exclude
list.
I'm gearing up for a 1.0 release this weekend, but the latest nightly
build available from the above URL should provide the functionality
you need. We're using this at work without problems, and I have a few
other users reporting great success.
Any feedback is appreciated!
Cheers,
Steve
--
Steve Webster
http://dynamicflash.com
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
