Thread: Re: [javaCompiler-users] Compiler "Install"
Status: Beta
Brought to you by:
soapy
From: xxxxxxxxxxxxxxxxxxxx x. <hul...@ya...> - 2007-01-16 12:27:25
|
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). 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. I'm using Windows XP Home. 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. (whether I just download the GUI frontend or also unpack the compilers into right directory doesn't make any difference to that) 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 " 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. Thanks again Peter >xxxxxxxxxxxxxxxxxxxx xxxxxxxxxx wrote: >> Hi Marco, >> >> I have recently learned of your compiler as an excellent way to turn >> java/swing applications native >It's still not 100% user friendly and you might need some missing libs. >Just contact me if you run into such problems... >> (until now I have used gcj for such >> purposes, but with imageio/swing there are obviously problems). >Yes, these don't work on Windows and where far from complete on Linux >the last time I tried. But the core compiler I use is also GCJ. >> Now I have a question regarding the "installation" process. Once I have >> downloaded all of the files, I try to open the JavaNativeCompiler.exe >> and nothing happens. If I attempt to execute the AutoCompiler.exe I get >> an exception during runtime initialisation - apparently the application >> requests the runtime to terminate. >What operating system do you use? Which version? The working directory >has to be the parent of the binaries. On Windows, this is the default if >you double click the binaries. On Linux, it's not (at least not on my >distro). >> I suppose I am doing something stupid I am not aware of?! >No, absolutely not. Just download the GUI frontend and start the >JavaNativeCompiler. The GUI will appear even if you have not yet >downloaded a compiler. >But better start with the AutoCompiler. What exception does it give? >Marco --------------------------------- Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends. |
From: Marco T. <mt...@gm...> - 2007-01-16 17:40:48
|
Hey Peter Can you please hit "Reply all"? Else we loose the mailing list. xxxxxxxxxxxxxxxxxxxx xxxxxxxxxx wrote: > Ok, did the manual compiling of a HelloWorld program and presto: > > All of the compiling seems to work fine, but when I then want to run my > HelloWorld app I get the same error I get when I try to start the > AutoCompiler: > > "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" Stupid! How did you compile? Did you enable optimization? Stripping? Adding debug info? Can you try a couple of different compilations? How much knowledge do you have with gcc and alike? Do you know how to add debuging information and run it in gdb? > So, for some reason my computer doesn't like files that have been > compiled with that jnc gcj.exe. Have you tried your compiled exe on another computer? > I was wondering whether my computer just starts loosing it, but if I > compile the same Hello World source code with my standard > cygwin-in-built gcj, everything works fine. Well, my gcj is built for mingw, but that really doesn't make a difference. Because it works on hundred of other computers (probably a lot of XP Homes), I assume it has something to do with your computer. What version is the cygwin gcj? > So, it is actually something about the jnc gcj.exe ...... can't really > think of something that my computer could do to "break" the jnc gcj > ..... any ideas? Hm. A compiled binary on windows uses ADVAPI32.dll, KERNEL32.dll, msvcrt.dll, USER32.dll and WS2_32.dll. Maybe you screwed one of these up? I really can't say anything better than to try on another computer. Sorry... Marco |
From: xxxxxxxxxxxxxxxxxxxx x. <hul...@ya...> - 2007-01-16 22:37:12
|
Hey Marco, solved the problem!! A few weeks ago I was messing with my cygwin install to get something working. I managed to do what I wanted to do, but as part of what I did I put a library file into the classpath (this time classpath is right!). That's what did the screwing up!! Removed it from the classpath now and jnc seems to work fine now. I could start the GUI and my manually compiled helloWorld app worked fine as well. So I reckon that's all of my problems solved. I'm working on an image-transforming app right now, so having a swing compatible native compiler like jnc is really useful. Before that I was mainly programming mathematical apps for research groups etc, so never had to deal with swing - mathematicians don't like pretty windows! Thanks for providing help on this one. And good work on jnc - keep it up All the Best Peter Marco Trudel <mt...@gm...> wrote: Hey Peter Can you please hit "Reply all"? Else we loose the mailing list. xxxxxxxxxxxxxxxxxxxx xxxxxxxxxx wrote: > Ok, did the manual compiling of a HelloWorld program and presto: > > All of the compiling seems to work fine, but when I then want to run my > HelloWorld app I get the same error I get when I try to start the > AutoCompiler: > > "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" Stupid! How did you compile? Did you enable optimization? Stripping? Adding debug info? Can you try a couple of different compilations? How much knowledge do you have with gcc and alike? Do you know how to add debuging information and run it in gdb? > So, for some reason my computer doesn't like files that have been > compiled with that jnc gcj.exe. Have you tried your compiled exe on another computer? > I was wondering whether my computer just starts loosing it, but if I > compile the same Hello World source code with my standard > cygwin-in-built gcj, everything works fine. Well, my gcj is built for mingw, but that really doesn't make a difference. Because it works on hundred of other computers (probably a lot of XP Homes), I assume it has something to do with your computer. What version is the cygwin gcj? > So, it is actually something about the jnc gcj.exe ...... can't really > think of something that my computer could do to "break" the jnc gcj > ..... any ideas? Hm. A compiled binary on windows uses ADVAPI32.dll, KERNEL32.dll, msvcrt.dll, USER32.dll and WS2_32.dll. Maybe you screwed one of these up? I really can't say anything better than to try on another computer. Sorry... Marco --------------------------------- Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. |
From: Marco T. <mt...@gm...> - 2007-01-17 10:02:12
|
xxxxxxxxxxxxxxxxxxxx xxxxxxxxxx wrote: > Hey Marco, > > solved the problem!! A few weeks ago I was messing with my cygwin > install to get something working. I managed to do what I wanted to do, > but as part of what I did I put a library file into the classpath (this > time classpath is right!). That's what did the screwing up!! Removed it > from the classpath now and jnc seems to work fine now. I could start the > GUI and my manually compiled helloWorld app worked fine as well. So I > reckon that's all of my problems solved. Can you explain that a little bit more? What file has it been? I'm surprised that one lib can stop GCC compiled apps from working... As long as it's not a Windows core dll, it really shouldn't have any impact... > I'm working on an image-transforming app right now, so having a swing > compatible native compiler like jnc is really useful. Before that I was > mainly programming mathematical apps for research groups etc, so never > had to deal with swing - mathematicians don't like pretty windows! :-) Well, If you have the choice, I suggest to use SWT instead of Swing. It's faster, looks better, has better native compilation support and creates way smaller binaries... > Thanks for providing help on this one. > And good work on jnc - keep it up Thanks and you're welcome... Marco |
From: xxxxxxxxxxxxxxxxxxxx x. <hul...@ya...> - 2007-01-24 22:16:40
|
FYI: I somehow had a libgcj jar in my classpath ... not exactly the thing you'd expect there! I'll think about switching to swt. Peter Marco Trudel <mt...@gm...> wrote: xxxxxxxxxxxxxxxxxxxx xxxxxxxxxx wrote: > Hey Marco, > > solved the problem!! A few weeks ago I was messing with my cygwin > install to get something working. I managed to do what I wanted to do, > but as part of what I did I put a library file into the classpath (this > time classpath is right!). That's what did the screwing up!! Removed it > from the classpath now and jnc seems to work fine now. I could start the > GUI and my manually compiled helloWorld app worked fine as well. So I > reckon that's all of my problems solved. Can you explain that a little bit more? What file has it been? I'm surprised that one lib can stop GCC compiled apps from working... As long as it's not a Windows core dll, it really shouldn't have any impact... > I'm working on an image-transforming app right now, so having a swing > compatible native compiler like jnc is really useful. Before that I was > mainly programming mathematical apps for research groups etc, so never > had to deal with swing - mathematicians don't like pretty windows! :-) Well, If you have the choice, I suggest to use SWT instead of Swing. It's faster, looks better, has better native compilation support and creates way smaller binaries... > Thanks for providing help on this one. > And good work on jnc - keep it up Thanks and you're welcome... Marco --------------------------------- Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. |
From: Marco T. <mt...@gm...> - 2007-01-16 16:36:48
|
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 |