(11-25-2022, 05:15 PM)mnrvovrfc Wrote:(11-25-2022, 11:07 AM)krovit Wrote: I'm not sure what you mean by the color "blue".Who cares? Because you didn't show the source code, that's what I meant "write something in blue (background)", didn't want to bore anybody with just saying, "We need to see the source code, error messages from the compiler aren't enough".
Usually the compiler shows the error during compilation but in this case it just says that there was an error and to look at the log. I can't understand the log (which shouldn't be surprising).
Basically I have no clue as to where the problem is!
Sell the application? Why? Who cares?
About QB version is 64bit and system is 64bit
"I have no clue as to where the problem is," if otherwise you aren't mixing and matching architectures then something else is wrong. If everything is 64-bit the mixing and matching library versions might be the culprit. Cannot use libraries furnished by the "QB64 Team" with everything else that belongs to QB64 Phoenix Edition.
You just gave us the error log but not the source code and that's why I said what I said. The compiler can only complain when it finds a reason for not generating an EXE file. I should have been more careful noticing that you're on Windows where the QB64 executable is furnished, not Linux where we have to create it from a script after having all the dependencies.
Anyway Doppler helped you better than I did.
Please note that I do not speak English and that the automatic translator sometimes chooses words that could be rude... It is easy not to understand each other or think that the other guy is a rude type.
However, there is no confusion between the files because it seems obvious to me that it is better to avoid extracting a new version on the old one. No... It's just a whole new folder. Only the source code is the old one.
Now I'm away from the workstation, tomorrow I'll put The screen shot of the error that, however, really does not seem to provide any clue.
Thank You