Are you on a VM?
I have 1GB on a machine where I build OM and I needed to set -Xmx and -Xms to
512M.
Maybe I could increase that a little but it compiles fine.
read JVMMEM
ORIGINAL=1024M
KEY=Xms
sed -i "s/<jvmarg value=\"-${KEY}${ORIGINAL}\" \/>\$/<jvmarg
value=\"-${KEY}${JVMMEM}\" \/>/g" build.xml
KEY=Xmx
sed -i "s/<jvmarg value=\"-${KEY}${ORIGINAL}\" \/>\$/<jvmarg
value=\"-${KEY}${JVMMEM}\" \/>/g" build.xml
--- On Fri, 2/22/13, [email protected] <[email protected]> wrote:
> Where did you change those settings?
> There are some settings inside the build file as well as you
> could set
> memory settings for ANT in general.
>
> But I am afraid the issue is more connected with memory
> restrictions of
> your system then with the settings for the build.
>
> Sebastian
>
>
> 2013/2/23 Rene' Rosenbaum <[email protected]>
>
> > Hi all,
> > I currently have problems compiling OM2.0 in a
> resource-limited Debian
> > 64bit installation. Calling "ant" without any
> parameters to build OM, the
> > process dies at
> > ---
> > compile.laszlo.main:
> >
> > -compile.flash:
> > [java] Error occurred during
> initialization of VM
> > [java] Could not reserve enough
> space for object heap
> > ---
> > Apparently, there is not enough memory. I already
> increased the system
> > memory from 512MB to 1024MB; without success. I can't
> imagine that
> > compiling OM2.0 requires more than that. Anyone, any
> idea what goes wrong
> > here or what can be done get over this issue? Many
> thanks in advance!
> >
> > Cheers,
> > Rene'
> > --
> >
> > ~~~~~~~
> > *Dr.-Ing. Rene' Rosenbaum
> > meeCoda* IT-Consulting and Services
> > ~: Neue Reihe 15, 18182 Goorstorf, Germany
> > #: ++49-(0)-1781408041
> > @:[email protected]
> <mailto:[email protected]>
> > //:www.meecoda.de <http://www.meecoda.de>
> > ~~~~~~~~~~~~~~ +++ ~~~~~~~~~~~~~~~~
> >
> >
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> [email protected]
>
