Is there a reason you would not set -static-link-runtime-shared-libraries to true when compiling an Actionscript project using mxmlc?
Is there a reason you would not set -static-link-runtime-shared-libraries to true when compiling an
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a reason you would not set -static-link-runtime-shared-libraries to true when compiling an Actionscript project using mxmlc?
If you have several applications for one project making the framework available as an RSL enables the other applications to load it from cache (it has been loaded there by the first app) and save bandwidth and time. If you set static linking to true, every application will contain the framework classes increasing your file sizes.
If you have only one application .swf, linking framework as an RSL can save bandwidth on updates – if only the main .swf changes, you can load it again bypassing the cache but load all the cached .swcs.