I'm tantalizingly close to making my own builds, which will make it possible
to start more interesting work on parpavm. I can make builds which xcode
successfully compiles and links, but which crash on running. I'm pretty
sure that's because I'm missing the secret sauce embedded in the
On Wednesday, April 26, 2017 at 8:44:26 AM UTC-7, Steve Hannah wrote:
>
> Oh. The ASM library. As far as I know we use the same version that is
> posted in cn1-binaries:
> https://github.com/codenameone/cn1-binaries/tree/master/vm
>
> That's the one I'm using, but it apparently isn't the one
Oh. The ASM library. As far as I know we use the same version that is
posted in cn1-binaries:
https://github.com/codenameone/cn1-binaries/tree/master/vm
Steve
On Wed, Apr 26, 2017 at 8:35 AM, Dave Dyer
wrote:
>
> On Wednesday, April 26, 2017 at 7:36:18 AM UTC-7,
On Wednesday, April 26, 2017 at 7:36:18 AM UTC-7, Steve Hannah wrote:
>
> What assembler are you referring to?
>
That would be the java bytecode assembler that ByteCodeTranslator uses to
map over the classes.
Seems to be part of android studio
--
You received this message because you are
What assembler are you referring to?
On Tue, Apr 25, 2017 at 7:54 PM, Dave Dyer
wrote:
>
> This discrepancy seems to be related to the version of the assembler that
> is used
> in the build. What version is being used by the build server?
>
> JAVA_OBJECT
This discrepancy seems to be related to the version of the assembler that
is used
in the build. What version is being used by the build server?
JAVA_OBJECT STATIC_FIELD_arimaa_ArimaaConstants_ArimaaId_ENUM_VALUES = 0;
> JAVA_OBJECT
>
Another discrepency between builds done today using the build server, and
builds I do myself
using today's copy of parpavm from the repository, which is causing my
local builds to fail to link
parpavm creates:
JAVA_OBJECT STATIC_FIELD_arimaa_ArimaaConstants_ArimaaId_ENUM_VALUES = 0;