Chris
Von: Justin Mclean
Gesendet: Montag, 19. September 2016 23:19:01
An: dev@flex.apache.org
Betreff: Re: mxmlc error null with "large" project
HI,
I do have a vague memory that it picks up the memory argument in different
spots depending if you have fork=“y
HI,
I do have a vague memory that it picks up the memory argument in different
spots depending if you have fork=“yes” or fork=“no”.
Justin
Alex,
Modifying the mxmlc jvm arguments did the trick.
Using "mxmlc jvmargs" in a google search found
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7fd9.html
which lead to the answer.
Thanks for the help.
Justin
On Mon, Sep 19, 2016 at 1:13 AM, Alex Harui wrote:
On 9/18/16, 7:02 PM, "Justin Magnan" wrote:
>I am having trouble with a build, I was hoping someone can help.
>
>
>This had me wondering if maybe ant was running out of memory, I looked at
>setting ANT_OPTS=-Xmx2098M, this did nothing.
>
>I then searched the web and found a couple links saying i
I am having trouble with a build, I was hoping someone can help.
We have a project with 2,774 files totaling 33.2 MB in size for the source.
Our build machine is a Linux box (8GB of memory) running the 4.14.1 SDK. We
use ant and flex tasks to execute our builds.
One of the guys on our team just
