Hi there,
vboxjmscom.jar is not with SDK. I am trying to compile from 4.0.4 ose source code in fedora core 14.
I was notified to set belows from other discussion.
CLASSPATH=some_where/jacob.jar
VBOX_WITH_JMSCOM=1
compilation is failed to build vboxjmscom.jar and belows errors was shown.
Is there anyone having hints to solute that? Any help is appreciated.
--brandon
kBuild: Generating Java MSCOM glue files from XIDL
kBuild: Generating Java interface files
filesplitter: Created 163 files.
kBuild: Generating Java glue files from XIDL
[glue-java.xsl] Error in Unhandled type: octet
kmk: *** [/home/user/Downloads/VirtualBox-4.0.4_OSE/out/linux.x86/release/obj/vboxjmscom-gen/jmscomgen/jmscomglue.list] Error 10
kmk: *** Waiting for unfinished jobs....
[glue-java.xsl] Error in fullClassName: Type "octet" is not supported.
kmk: *** [/home/user/Downloads/VirtualBox-4.0.4_OSE/out/linux.x86/release/obj/vboxjxpcom-gen/jxpcomgen/jxpcomglue.list] Error 10
rm /home/user/Downloads/VirtualBox-4.0.4_OSE/out/linux.x86/release/obj/pcnet32.rom.rt2.bin /home/user/Downloads/VirtualBox-4.0.4_OSE/out/linux.x86/release/obj/pcnet32.rom.rt2.zbin
problem to build vboxjmscom.jar
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: problem to build vboxjmscom.jar
These are results. What about the configure statements and LocalConfig.kmk.
Have you installed all the needed packages?
How are you trying to setup the compile?
What are you trying to achieve? Compile VBox with webservice?
Provide the configure.log from the top level directory and the LocalConfig.kmk.
This may help http://forums.virtualbox.org/viewtopic.php?f=31&t=35892
Have you installed all the needed packages?
How are you trying to setup the compile?
What are you trying to achieve? Compile VBox with webservice?
Provide the configure.log from the top level directory and the LocalConfig.kmk.
This may help http://forums.virtualbox.org/viewtopic.php?f=31&t=35892
-
- Posts: 10
- Joined: 26. Jul 2008, 14:13
Re: problem to build vboxjmscom.jar
Perryg, thanks for response.
I want WIndows Java COM bindings (vboxjmscom.jar) which is not shipped with current 4.0.4 sdk.
From http://www.mail-archive.com/vbox-dev@vi ... 03625.html , It seems only way to have it
is to compile from source code. To have the vboxjmscom.jar need to VBOX_WITH_JMSCOM=1 and
the jacob jar to in classpath. My fc14 has the all required packages for compilation. Run "configure" does
not product any error".
The compilation is failed at the stage of making glue layer ( as guess from the errors messages returned:
"[glue-java.xsl] Error in Unhandled type: octet")
kBuild: Generating Java interface files
filesplitter: Created 163 files.
kBuild: Generating Java glue files from XIDL
[glue-java.xsl] Error in Unhandled type: octet
kmk: *** [/root/Desktop/VirtualBox-4.0.4_OSE/out/linux.amd64/release/obj/vboxjmscom-gen/jmscomgen/jmscomglue.list] Error 10
kmk: *** Waiting for unfinished jobs....
filesplitter: Created 165 files.
kmk: *** Exiting with status 2
Starts wondering if this is a bug in current 4.0.4 source tree. Same steps are used to compile in svn source tree. It is sucessful to have vboxjmscom.jar to build. Unfortunately, it products the one of the version 4.1, not 4.0.4.
I want WIndows Java COM bindings (vboxjmscom.jar) which is not shipped with current 4.0.4 sdk.
From http://www.mail-archive.com/vbox-dev@vi ... 03625.html , It seems only way to have it
is to compile from source code. To have the vboxjmscom.jar need to VBOX_WITH_JMSCOM=1 and
the jacob jar to in classpath. My fc14 has the all required packages for compilation. Run "configure" does
not product any error".
The compilation is failed at the stage of making glue layer ( as guess from the errors messages returned:
"[glue-java.xsl] Error in Unhandled type: octet")
kBuild: Generating Java interface files
filesplitter: Created 163 files.
kBuild: Generating Java glue files from XIDL
[glue-java.xsl] Error in Unhandled type: octet
kmk: *** [/root/Desktop/VirtualBox-4.0.4_OSE/out/linux.amd64/release/obj/vboxjmscom-gen/jmscomgen/jmscomglue.list] Error 10
kmk: *** Waiting for unfinished jobs....
filesplitter: Created 165 files.
kmk: *** Exiting with status 2
Starts wondering if this is a bug in current 4.0.4 source tree. Same steps are used to compile in svn source tree. It is sucessful to have vboxjmscom.jar to build. Unfortunately, it products the one of the version 4.1, not 4.0.4.
- Attachments
-
- configure.log
- configure.log
- (14.28 KiB) Downloaded 36 times
-
- Posts: 10
- Joined: 26. Jul 2008, 14:13
[solved] Re: problem to build vboxjmscom.jar
Eventually, It is successfully to build vboxjmscom.jar from 4.1.16 source. I attach it here for people who
have difficulty to find one. But I haven't tested it with application yet.
It is a bug in java-glue.xsl for generating Helper.java correctly for building vboxjmscom.jar .
Hope the developers can fix it soon.
For 4.0.x, a different bug exists in java-glue.xsl. But unlike 4.1.x, don't know how to patch it to have a good build.
have difficulty to find one. But I haven't tested it with application yet.
It is a bug in java-glue.xsl for generating Helper.java correctly for building vboxjmscom.jar .
Hope the developers can fix it soon.
For 4.0.x, a different bug exists in java-glue.xsl. But unlike 4.1.x, don't know how to patch it to have a good build.
- Attachments
-
- vboxjmscom.zip
- (190.75 KiB) Downloaded 92 times
-
- Posts: 10
- Joined: 26. Jul 2008, 14:13
Re: problem to build vboxjmscom.jar
Eventually, an application is developed using vboxjmscom.jar, see below
http://vmmgrs.hopto.org/
But it seems there're bugs, some APIs always cause below exception,
INFO: java.lang.IllegalStateException: getInt() only legal on Variants of type VariantInt, not 19
An examples of problem APIs are IHost.getMemorySize(), IHost.getProcessorCount(), they are supposed
to return a long value instead of causing exception. Anyone know the proper place to report this?
http://vmmgrs.hopto.org/
But it seems there're bugs, some APIs always cause below exception,
INFO: java.lang.IllegalStateException: getInt() only legal on Variants of type VariantInt, not 19
An examples of problem APIs are IHost.getMemorySize(), IHost.getProcessorCount(), they are supposed
to return a long value instead of causing exception. Anyone know the proper place to report this?