Re: [javaCompiler-users] Compiler "Install"

[Marco T. <mt...@gm...>]

xxxxxxxxxxxxxxxxxxxx xxxxxxxxxx wrote:
> Hi,
> 
> thanks for the quick answer.
> I'm pretty sure that the problem I've got is to do with the GUI 
> frontend. The compiler binaries all seem to work (did a few manual test 
> compilations).

Great, someone who knows what he's doing. That will make it easier :-)
The GUI frontend and AutoCompiler are both written in Java and compiled 
with JNC (GCJ) itself. So can you please compile a simple "Hello World" 
application with the provided GCJ and see if that runs on your computer? 
You have to add "-ljncTrial", else you will get a license error.


> The problem is that the GUI just won't appear when I try to start the 
> JavaNativeCompiler nor will I get any sort of feedback at all.

Yes, thats because the console is suppressed. You can run "AutoCompiler 
-debug", that will start the GUI and keep the console open. But because 
AutoCompiler itself doesn't work on your computer, that's not much of 
use and leaves us with working with AutoCompiler since there we see the 
output.


> I'm using Windows XP Home.

Can you try it on another computer? I tested a lot of Windows XP 
Professional and Home and had never problems. Someone once had a problem 
with the GUI, but AutoCompiler worked. We then decided that his computer 
  was somehow screwed up since all others he had worked.
So, something really has to be special on your computer...


> Apart from the obvious double-clicking on it, I also tried to get it to 
> go via the standard windows command/cygwin bash shells, so I haven't 
> tried any fancy workarounds yet.

Not needed. Doubleclicking really should be enough.


> (whether I just download the GUI 
> frontend or also unpack the compilers into right directory doesn't make 
> any difference to that)

Yes, doesn't matter. The compilers are only needed in the final step.


> As for the AutoCompiler: When I start it via a shell (otherwise I just 
> get a shell that pops up and immediately disappears), I get the 
> following message:
> "
> Exception during runtime initialisation
> 
> This application has requested the runtime to terminate it in an unusual 
> way.
> Please contact the application's support team for more information
> "

Very very strange. I never heard that and you're the first of thousands 
of users reporting something like that. So I can't debug it because I 
can't duplicate it... I think we're best off with you trying to compile 
something manually to see if that works...


> Once I get the GUI to work, I reckon the rest should take care of 
> itself. I could probably just use the compilers manually, but I might 
> get conflicting CLASSPATH problems if I keep my standard gcj etc. in 
> there as well, which I would quite like to.

I assume you mean "PATH" ;-) Yes, there you would probably get into 
trouble. A really ugly workaround would be to always call it absolutely. 
But using the GUI is definitely the better idea since a couple of 
special flags are required depending on what you do.

Please try a very minimalistic Java application. If that runs, it 
becomes even more strange. I'm interested in your feedback...


Marco