Skip to main content

problems during midp compiling

4 replies [Last post]
davidy
Offline
Joined: 2007-04-18

There are two questions when i built midp component. I used the template of linux_fb_gcc on the platform of linux_i386
1.The 'merged.xml' file is generated by Makefile. There is a key-word like 'KeyValue=""'. Why the 'KeyValue' has null value and how to config this value?
example:
***********************

***********************
2.During compiling the java files, errors were reported that lots of java classes can't find 'ResourceConstants' and 'LogChannels' classes. such as:
***********************
EventQueue.java:35: cannot find symbol
symbol : class LogChannels
location: package com.sun.midp.log
import com.sun.midp.log.LogChannels;
***********************
Whether is another option that I set incorrectly?
Thanks

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
davidy
Offline
Joined: 2007-04-18

I had changed my [b]sdk[/b] to version 1.4.2_14, but it doesn't work still. I can get this jar file, but as what I listed before, the contant files weren't generated correctly. In the generated document, there are some files generated by Configurator.jar(midp_constants_data.h etc), the contents of these files, however, are almost empty. I guess this jar file should generate another constant java files like "ResourceConstants.java" and "LogChannels.java", unfortunately, it wasn't. I'm totally confused by this phenomena. What should I do next? Thanks

davidy
Offline
Joined: 2007-04-18

I examined the problem all day, finally I found it due to the "malfunction" of the Configurator which changes the Input files(.xml) to the Constant and Property output files(such as Constants.java and .h .c etc). I used the default sets on the target of linux_fb_gcc, but the Configurator didn't work and these files were not generated correctly which I had listed yesterday. I'm out of my mind, so I beg your answer. Thanks

alexey_z
Offline
Joined: 2006-10-18

What do you mean by "malfunction": the Configurator wasn't built, or it was built but doesn't work properly? To find this out, you can check if Configurator.jar (and com/.../CodeTransformer.class) exists in the tools output directory ($TOOLS_DIR/output by default). Also ensure that you use jdk 1.4.x, phoneME Feature may not be compiled with 1.5.

Regards,
Alexey

davidy
Offline
Joined: 2007-04-18

Thanks alexey_z for gaving me the correct solution on my problem. When I changed the jdk version from 1.5.0_11 to 1.4.2_14, I passed through the MIDP compiling. There must be some conficts between CodeTransformer.java and jdk 1.5.0, but it doesn't mean that all the 1.5.* versions exist this problem. May be someone will give us the answer.
Thanks again