This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
DCH> I've been corresponding with Erik Poupaert on this. His advice DCH> suggests that my problem is due to not having VC.NET installed DCH> on this machine. Would you agree that VC.NET is required? >>>>VC.NET is not required unless you are trying to build the DLL itself. This is how the statically linked controlexample was built. You can perfectly well build it dynamically linked against the JNI dll. DCM> If I link to the Win32 libs (on Erics advice) when building the DCM> exe (add -lole32 -lcomctl32, etc.) the app runs, does not give DCM> and NPE but the VM exits imediatly and the Shell flashes up and DCM> disapears just *after* the VM exits - very strange. >>>> I didn't have to do any of that... have a look at the following message, >>>> it includes a couple of attachments, look in the "build-swt.sh", that >>>> takes care of the whole swt build process : >>>>>>> As long as you down want to re-build the SWT dll it should be easy. The reason I sent you the statically linked controlexample, is in order to figure out if it works on NT4SP6, since it works fine on win98SE and win2KSP. Now, you wrote to me that it works fine. So, there is no reason to think that SWT applications do not work on NT4SP6.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |