Windows target build error

16 views
Skip to first unread message

Bryan Buchanan

unread,
Jun 15, 2016, 3:51:08 AM6/15/16
to CodenameOne Discussions
App build fine for Android target, but barfs on this error for Windows build:

Executing: c:\Program Files\Java\jdk1.8.0_60\bin\java -Dretrolambda.inputDir=C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\classes -Dretrolambda.classpath=C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\classes;C:\Users\Shai\AppData\Local\Temp\temp1494808247609234705.jar -Dretrolambda.outputDir=C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\classes_retrolamda -Dretrolambda.bytecodeVersion=49 -Dretrolambda.defaultMethods=true -jar C:\Users\Shai\AppData\Local\Temp\temp2124066438512708944.jar Retrolambda 2.0.3
Bytecode version: 49 (Java 5)
Default methods:  true
Input directory:  C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\classes
Output directory: C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\classes_retrolamda
Classpath:        C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\classes;C:\Users\Shai\AppData\Local\Temp\temp1494808247609234705.jar
Saving lambda class: com/nutmeg/survey/Form3$$Lambda$1
Saving lambda class: com/nutmeg/survey/Form4$$Lambda$1
Saving lambda class: com/nutmeg/survey/Form1$$Lambda$1
Saving lambda class: com/nutmeg/survey/Form2$$Lambda$1
Executing: java -Xmx1024m -jar win_xmlvm.jar --in=C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\classes_retrolamda --resource=C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\Main\Main\res/ --out=C:\Users\Shai\AppData\Local\Temp\build1466699689663839410xxx\Main\Main\src --target=csharp --app-name=Main Exception in thread "main" java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at com.simontuffs.onejar.Boot.run(Boot.java:306)
	at com.simontuffs.onejar.Boot.main(Boot.java:159)
Caused by: com.android.dx.cf.code.SimException: not an array type: I
	at com.android.dx.cf.code.BytecodeArray.parseInstruction(BytecodeArray.java:793)
	at com.android.dx.cf.code.Simulator.simulate(Simulator.java:99)
	at com.android.dx.cf.code.Ropper.processBlock(Ropper.java:678)
	at com.android.dx.cf.code.Ropper.doit(Ropper.java:633)
	at com.android.dx.cf.code.Ropper.convert(Ropper.java:250)
	at org.xmlvm.proc.out.DEXmlvmOutputProcess.processMethod(DEXmlvmOutputProcess.java:958)
	at org.xmlvm.proc.out.DEXmlvmOutputProcess.process(DEXmlvmOutputProcess.java:673)
	at org.xmlvm.proc.out.DEXmlvmOutputProcess.generateDEXmlvmFile(DEXmlvmOutputProcess.java:423)
	at org.xmlvm.proc.out.DEXmlvmOutputProcess.generateDEXmlvmFile(DEXmlvmOutputProcess.java:373)
	at org.xmlvm.proc.out.DEXmlvmOutputProcess.processPhase1(DEXmlvmOutputProcess.java:345)
	at org.xmlvm.proc.XmlvmProcessImpl.forwardOrProcessPhase1(XmlvmProcessImpl.java:209)
	at org.xmlvm.proc.XmlvmProcessImpl.forwardOrProcessPhase1(XmlvmProcessImpl.java:206)
	at org.xmlvm.proc.XmlvmProcessImpl.forwardOrProcessPhase1(XmlvmProcessImpl.java:206)
	at org.xmlvm.proc.XmlvmProcessImpl.forwardOrProcessPhase1(XmlvmProcessImpl.java:206)
	at org.xmlvm.proc.XmlvmProcessor.process(XmlvmProcessor.java:157)
	at org.xmlvm.proc.XmlvmProcessor.process(XmlvmProcessor.java:137)
	at org.xmlvm.Main.main(Main.java:53)
	... 6 more
Caused by: java.lang.IllegalArgumentException: not an array type: I
	at com.android.dx.rop.type.Type.getComponentType(Type.java:789)
	at com.android.dx.cf.code.Simulator$SimVisitor.visitNoArgs(Simulator.java:326)
	at com.android.dx.cf.code.BytecodeArray.parseInstruction(BytecodeArray.java:541)
	... 22 more

Shai Almog

unread,
Jun 16, 2016, 12:25:55 AM6/16/16
to CodenameOne Discussions
This is the old Windows Phone build target and not the new UWP target. It has issues with multi-dimension arrays that we tried to workaround but it's a pretty problematic port.
Reply all
Reply to author
Forward
0 new messages