|The thing is that when Java is installed it doesn't add some kind of dynamic link in PATH to where
jvm.dll is located, well it doesn't add one at all.
Yes, if I'm compiling the class with 1.8 and then on VM I can manually add in PATH the server folder, but here is a problem, the user should not go though this process of opening variables and find PATH to add it there.
A solution would be that when the app is opened, it would check if Java in installed, if it is not, then the user would be prompted to download it, or I have to search and see if you can legally distribute
JavaSetup8uxxx.exe file and if you can the app would automatically run the file and the user would go though the process of installing Java. After Java is installed by either way then the app will search what version is installed to know what location to add in PATH, which it would do after knowing that. At this point the app will run fine.
BUT then you run into another problem, if the user updates Java then the location will change for
jvm.dll, so you would have to add another variable to PATH with the new location for it, and remove the old one.
Adding a variable to PATH shouldn't be a problem, as Java and other programs do it too, I'll just have to see how that is done from C++ code.
If this is actually the only way to do it, then I guess I can do it this way, but having another solution that wouldn't involve adding variables to PATH would have been better.